8224 ETHERNET STACKABLE HUB GA27-4024-02

INSTALLATION AND USER'S GUIDE

IBM 8224 ETHERNET STACKABLE HUB GA27-4024-02

INSTALLATION AND USER'S GUIDE

+--- NOTE -----------------------------------------------------------+
| |
| Before using this information and the product it supports, be sure |
| to read the general information in Appendix F, "Notices and |
| Product Warranty." |
| |
+--------------------------------------------------------------------+

THIRD EDITION (JUNE 1996)

THE FOLLOWING PARAGRAPH DOES NOT APPLY TO THE UNITED KINGDOM OR ANY
COUNTRY WHERE SUCH PROVISIONS ARE INCONSISTENT WITH LOCAL
LAW: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do
not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.

This publication could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or
program(s) described in this publication at any time.

It is possible that this publication may contain reference to, or
information about, IBM products (machines and programs), programming,
or services that are not announced in your country. Such references
or information must not be construed to mean that IBM intends to
announce such IBM products, programming, or services in your country.

Requests for technical information about IBM products should be made
to your IBM Authorized Dealer or your IBM Marketing Representative.

A form for readers' comments appears at the back of this publication.
If the form has been removed, address your comments to:

Department CGF
Design & Information Development
IBM Corporation
PO Box 12195
RESEARCH TRIANGLE PARK NC 27709-9990
USA

When you send information to IBM, you grant IBM a nonexclusive right
to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.

(C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1994, 1996.
ALL RIGHTS RESERVED.
Note to U.S. Government Users -- Documentation related to restricted
rights -- Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.

CONTENTS
________

Safety Notices . . . . . . . . . . . . . . . . . . . x

ABOUT THIS MANUAL . . . . . . . . . . . . . . . . XXIII
Who Should Read This Manual . . . . . . . . . . . xxiii
How This Manual Is Organized . . . . . . . . . . xxiii
Technical and Planning References . . . . . . . . . xxv

CHAPTER 1. INTRODUCTION AND PLANNING . . . . . . . 1-1
The 8224 . . . . . . . . . . . . . . . . . . . . . 1-1
Features . . . . . . . . . . . . . . . . . . . . 1-2
Interconnecting Typical Ethernet Hubs . . . . . . 1-4
Interconnecting 8224s . . . . . . . . . . . . . . 1-4
Understanding Managed Stacks . . . . . . . . . . . 1-5
Inter-8224 Communications in Managed Stacks . . . 1-5
Why Segment 8224s from a Stack? . . . . . . . . . 1-6
Segmenting 8224s from a Stack . . . . . . . . . . 1-7
Linking Segmented 8224s . . . . . . . . . . . . . 1-7
Assigning Backup Ports . . . . . . . . . . . . . . 1-9
Ethernet Planning . . . . . . . . . . . . . . . . . 1-9
Four-Repeater Limit . . . . . . . . . . . . . . 1-10
Maximum Segment Lengths . . . . . . . . . . . . 1-10
Maximum Distance Limit (Optical Fiber Only) . . 1-10
Power Loss Budgeting (Optical Fiber Only) . . . 1-13
Cables and Connectors . . . . . . . . . . . . . . 1-15
Cabling Requirements for 10BASE-T Ports . . . . 1-15
Cabling Requirements for Media Expansion Ports 1-16
Cabling Requirements for Hub Expansion Ports . 1-16
Cabling Requirements for the Com Port . . . . . 1-16
Protected Vital Configuration Data . . . . . . . 1-17
Power Requirements and Characteristics . . . . . 1-17
AC Power Input . . . . . . . . . . . . . . . . 1-17
DC Power Input . . . . . . . . . . . . . . . . 1-18
Physical Characteristics . . . . . . . . . . . . 1-19
Operating Environment . . . . . . . . . . . . . . 1-19
Space Requirements . . . . . . . . . . . . . . 1-19
Environmental Requirements . . . . . . . . . . 1-19
Acoustic Characteristics . . . . . . . . . . . . 1-20
Filling Out the Planning Charts . . . . . . . . . 1-20
Filling Out the Rack Inventory Chart . . . . . 1-21
Filling Out the IBM 8224 Stack Chart . . . . . 1-21
Filling Out the IBM 8224 Setup and Cabling Chart 1-21

CHAPTER 2. INSTALLING THE 8224 . . . . . . . . . . 2-1
Before You Begin . . . . . . . . . . . . . . . . . 2-1
Setup . . . . . . . . . . . . . . . . . . . . . . . 2-2
Rack-Mounting the 8224 . . . . . . . . . . . . . 2-2
Surface-Mounting the 8224 . . . . . . . . . . . . 2-4
Installing a Media Expansion Port Module . . . . . 2-4

Connecting Cables . . . . . . . . . . . . . . . . . 2-5
Connecting a Cable to the Media Expansion Port 2-5
Connecting Cables to 10BASE-T Ports . . . . . . . 2-6
Connecting Cables to the Hub Expansion Ports . . 2-7
Connecting a Modem or a Null-Modem Cable to the
Com Port . . . . . . . . . . . . . . . . . . . . 2-7
Connecting Power to the 8224 . . . . . . . . . . . 2-8
AC Power . . . . . . . . . . . . . . . . . . . . 2-8
DC Power . . . . . . . . . . . . . . . . . . . . 2-9
Switching On the 8224 . . . . . . . . . . . . . . 2-10

CHAPTER 3. 8224 ADMINISTRATION . . . . . . . . . . 3-1
Administrative Options Available for Any 8224 Setup 3-4
Understanding the LEDs . . . . . . . . . . . . . 3-4
Getting New Microcode . . . . . . . . . . . . . . 3-6
Upgrading Microcode Using XMODEM . . . . . . . . 3-8
Splitting a Stack . . . . . . . . . . . . . . . 3-10
Preparing for SNMP Management . . . . . . . . . . 3-10
Getting Started: SNMP over IP . . . . . . . . . 3-11
Managing 8224s Using SNMP . . . . . . . . . . . . 3-16
Inter-8224 Communications and the StackTable . 3-17
Segmenting an 8224 from a Stack . . . . . . . . 3-17
Enabling or Disabling Ports . . . . . . . . . . 3-17
Assigning Backup Ports . . . . . . . . . . . . 3-17
Getting Performance Statistics . . . . . . . . 3-18
Getting Error Statistics . . . . . . . . . . . 3-18
Receiving Traps . . . . . . . . . . . . . . . . 3-19
SNMP Management through the Com Port . . . . . . 3-20
Assigning an IP Address and Subnet Mask to the
Com Port . . . . . . . . . . . . . . . . . . . 3-20
Starting a SLIP Session . . . . . . . . . . . . 3-20
Assigning Default Gateways to the Stack . . . . 3-21
Upgrading Microcode Using TFTP . . . . . . . . . 3-23
MIB-Triggered Upgrade through Any Ethernet Port 3-23
MIB-Triggered Upgrade through the Com Port . . 3-24
BootP-Triggered Upgrade . . . . . . . . . . . . 3-26
Managing the 8224 Using the VT100 Interface . . . 3-27
Communication Alternatives . . . . . . . . . . 3-27
VT100 Panels . . . . . . . . . . . . . . . . . 3-28
Port Intrusion Protection . . . . . . . . . . . . 3-48
Activating Intrusion Protection . . . . . . . . 3-48
Intrusion Detection . . . . . . . . . . . . . . 3-49
Security . . . . . . . . . . . . . . . . . . . 3-49
Auto-discovery . . . . . . . . . . . . . . . . . 3-49
IP Auto-discovery . . . . . . . . . . . . . . . 3-49
Novell IPX Auto-discovery . . . . . . . . . . . 3-50
RJ-45 Auto-polarity Reversal . . . . . . . . . . 3-50

CHAPTER 4. SERVICING 8224S . . . . . . . . . . . . 4-1
Hot-Swapping 8224s . . . . . . . . . . . . . . . . 4-1
Parts . . . . . . . . . . . . . . . . . . . . . . . 4-3

APPENDIX A. PLANNING CHARTS . . . . . . . . . . . A-1

iv 8224 Ethernet Stackable Hub

APPENDIX B. CABLE PINOUT DIAGRAMS . . . . . . . . B-1
Straight-Through 10BASE-T Cables . . . . . . . . B-1
Crossover 10BASE-T Cables . . . . . . . . . . . . B-1
Hub Expansion Cable . . . . . . . . . . . . . . . B-2

APPENDIX C. VALIDATING IP AND NETMASK ADDRESSES C-1
Converting Between Decimal and Binary Values . . C-1
Logically ANDing an IP Address and a Subnet Mask C-2

APPENDIX D. THE IBM 8224 MANAGEMENT INFORMATION
BASE . . . . . . . . . . . . . . . . . . . . . . . D-1

APPENDIX E. ETHERNET FRAME FORMAT SUPPORT . . . . E-1
Frame Formats . . . . . . . . . . . . . . . . . . . E-1
Extended Ethernet Frame Formats . . . . . . . . . . E-2
Supported Frame Formats . . . . . . . . . . . . . . E-3

APPENDIX F. NOTICES AND PRODUCT WARRANTY . . . . . F-1
Electronic Emission Notices . . . . . . . . . . . . F-1
Lithium Battery Notice . . . . . . . . . . . . . . F-6
Lithium Battery . . . . . . . . . . . . . . . . . F-6
Pile au lithium . . . . . . . . . . . . . . . . . F-6
Litiumbatteri . . . . . . . . . . . . . . . . . . F-6
DC Power Cables Notice . . . . . . . . . . . . . . F-6
Trademarks . . . . . . . . . . . . . . . . . . . . F-7
Warranty . . . . . . . . . . . . . . . . . . . . . F-8

APPENDIX G. HELP AND SERVICE INFORMATION . . . . . G-1
Step 1: Troubleshooting . . . . . . . . . . . . . G-1
Step 2: Preparing for the Call . . . . . . . . . . G-1
Step 3: Placing the Call to IBM . . . . . . . . . G-2

GLOSSARY . . . . . . . . . . . . . . . . . . . . . X-1

INDEX . . . . . . . . . . . . . . . . . . . . . . X-19

Contents v

vi 8224 Ethernet Stackable Hub

FIGURES
_______

1-1. Front View of the IBM 8224 Ethernet
Stackable Hub Models xx1 and xx2 . . . . . 1-1
1-2. Hubs B and C Are Cascaded from Hub A . . . 1-4
1-3. A Stack of Four Model xx1s . . . . . . . . 1-4
1-4. A Managed Stack of 8224s . . . . . . . . . 1-5
1-5. Hub B Is Segmented from the External
Ethernet Bus . . . . . . . . . . . . . . . 1-7
1-6. Hub C Is Cascaded from Hub B . . . . . . . 1-8
1-7. Hub C Is Segmented but Manageable through
the Switch . . . . . . . . . . . . . . . . 1-8
1-8. Backup Connection from Hub C to a LAN Switch 1-9
1-9. An Example Network with an Optical Fiber
Link . . . . . . . . . . . . . . . . . . 1-12
1-10. RJ-45 Connector for 10BASE-T . . . . . . 1-15
2-1. Contents of the 8224 Package . . . . . . . 2-1
2-2. Rotating the Rack-Mounting Brackets . . . . 2-2
2-3. Attaching the Cable Management Bracket . . 2-2
2-4. Special Mounting Brackets for Models 481 and
482. . . . . . . . . . . . . . . . . . . . 2-3
2-5. Front Views of the Media Expansion Port
Modules . . . . . . . . . . . . . . . . . . 2-4
2-6. Location of the Media Expansion Port . . . 2-4
2-7. Inserting a Media Expansion Port Module . . 2-4
2-8. Location of the Uplink Switch . . . . . . . 2-6
2-9. Location of the Com Port . . . . . . . . . 2-7
2-10. Connecting the AC Power Cord to Models 001
or 002 . . . . . . . . . . . . . . . . . . 2-8
2-11. Rear View of the 8224 Model 481 or 482. . . 2-9
2-12. DC Power Terminal Block on the 8224 Model
481 or 482 . . . . . . . . . . . . . . . . 2-9
3-1. Front View of the 8224 Models xx1 and xx2 3-4
3-2. A Sample Microcode Upgrade Request File . . 3-9
3-3. A Sample Configuration File . . . . . . . 3-12
3-4. A Sample BootP Configuration File . . . . 3-15
3-5. A Sample BootP/TFTP Download File . . . . 3-26
4-1. 8224 Parts . . . . . . . . . . . . . . . . 4-3
A-1. Rack Inventory Chart . . . . . . . . . . . A-2
A-2. IBM 8224 Stack Chart . . . . . . . . . . . A-2
A-3. IBM 8224 Setup and Cabling Chart . . . . . A-2
B-1. Straight-Through UTP Cable (RJ-45 to RJ-45),
T568-A . . . . . . . . . . . . . . . . . . B-1
B-2. Straight-Through UTP Cable (RJ-45 to RJ-45),
T568-B . . . . . . . . . . . . . . . . . . B-1
B-3. Straight-Through STP Cable (RJ-45 to IBM
Data Connector) . . . . . . . . . . . . . . B-1
B-4. Crossover UTP Cable (RJ-45 to RJ-45), T568-A B-1
B-5. Crossover UTP Cable (RJ-45 to RJ-45), T568-B B-2

B-6. Crossover STP Cable (RJ-45 to IBM Data
Connector) . . . . . . . . . . . . . . . . B-2
B-7. Hub Expansion Cable, T568-A . . . . . . . . B-2
B-8. Hub Expansion Cable, T568-B . . . . . . . . B-2
E-1. Ethernet II Frame Format . . . . . . . . . E-1
E-2. IEEE 802.3 Frame Format . . . . . . . . . . E-2
E-3. 802.2 LLC Header . . . . . . . . . . . . . E-2
E-4. 802.2 SNAP Header . . . . . . . . . . . . . E-3

viii 8224 Ethernet Stackable Hub

TABLES
______

1-1. Maximum Segment Lengths for the Supported
Ethernet Types . . . . . . . . . . . . . 1-10
1-2. Equivalent Distances for Signals Passing
Through an 8224 . . . . . . . . . . . . . 1-11
1-3. 8224 Optical Fiber MEP Power Budgets . . 1-13
1-4. Noise Emission Characteristics of the 8224 1-20
3-1. Administrative Actions Available for
Unmanaged Stacks . . . . . . . . . . . . . 3-1
3-2. Administrative Actions Available for Managed
Stacks . . . . . . . . . . . . . . . . . . 3-3
3-3. 8224 Status LEDs . . . . . . . . . . . . . 3-5
3-4. 10BASE-T Port Status LEDs . . . . . . . . . 3-6
4-1. Parts List . . . . . . . . . . . . . . . . 4-3

Figures ix

SAFETY NOTICES
______________

DANGER

Turn power off and unplug the power cord from the
receptacle before connecting or disconnecting signal
cables.

GEVAAR !

Zet de netschakelaar op O (Uit) en trek de stekker uit
het stopcontact vooraleer u signaalkabels los-of
vastkoppelt.

PERIGO

Desligue a forca e desconecte o cabo de forca da caixa
antes de conectar ou desconectar os cabos de sinal.

DANGER !

Mettez le controleur hors tension et retirez le cordon
d'alimentation de sa prise, avant de connecter ou de
deconnecter les cables d'interface.

FARE!

For signalkablerne tilsluttes eller afmonteres:
Sluk for strommen, og traek netledningen ud af
stikkontakten.

VAARA

Katkaise virta ja irrota verkkojohto pistorasiasta, ennen
kuin kyket tai irrotat liitaentaekaapeleita.

DANGER !

Mettez l'interrupteur de tension hors tension et
debranchez le cordon d'alimentation de la prise avant de
connecter ou de deconnecter des cables de transmission.

x 8224 Ethernet Stackable Hub

VORSICHT

Aus Sicherheitsgruenden ist der Netzstecker zu ziehen,
bevor Signalkabel angeschlossen oder aufgetrennt werden.

PERICOLO

Spegnere l'unita e scollegare il cavo di alimentazione
dalla presa, prima di collegare o scollegare i cavi
segnali.

FARE

Sla av nettspenningen og trekk nettkabelen ut av
kontakten for du tar ut eller kopler til signalkabler.

PERIGO

Desligue a corrente e retire o cabo de corrente electrica
da tomada, antes de ligar ou de desligar os cabos de
sinal.

PELIGRO

Apague la alimentacion electrica del equipo y desenchufe
el cable del receptaculo antes de conectar o desconectar
cables de senal.

VARNING -- LIVSFARA

Sla fran stroemmen och lossa naetkabeln fran eluttaget
innan du ansluter eller kopplar ur signalkablar.

DANGER

To avoid shock hazard:

o The power cord must be connected to a properly wired
and earthed receptacle.
o Any equipment to which this product will be attached
must also be connected to properly wired receptacles.

Tables xi

GEVAAR !

Om elektrische schokken te vermijden:

o moet het netsnoer aangesloten zijn op een correct
bedraad en geaard stopcontact.
o moeten alle machines waarmee dit product zal worden
verbonden ook op correct bedrade stopcontacten zijn
aangesloten.

PERIGO

Para evitar perigo de choque:

o O cabo de forca deve estar conectado a tomadas com
fios e aterramento adequados.
o Qualquer equipamento ao qual este produto seja ligado
tambem devera estar conectado a tomadas com fiacao
adequada.

DANGER:

Pour eviter tout risque de choc electrique:

o Le cordon d'alimentation doit etre branche sur une
prise d'alimentation correctement cablee et mise a la
terre.
o D'autre part, tout le materiel connecte a ce produit
doit egalement etre branche sur des prises
d'alimentation correctement cablees et mises a la
terre.

FARE!

Undga elektrisk stod:

o Netledningen skal tilsluttes en korrekt installeret
stikkontakt med forbindelse til jord.
o Sorg for korrekt installation af stikkontakterne,
bade til produktet og til det udstyr, det tilsluttes.

xii 8224 Ethernet Stackable Hub

VAARA

Voit saada saehkoeiskun, jos et noudata seuraavia
ohjeita:

o Taemaen laitteen verkkojohdon saa kytkeae vain
toimintakunnossa olevaan maadoitettuun pistorasiaan.
o Taehaen laitteeseen liitettaevaet laitteet on
kytkettaevae toimintakunnossa olevaan maadoitettuun
pistorasiaan.

DANGER

Pour eviter tout risque de choc electrique:

VORSICHT

Aus Sicherheitsgruenden

o Geraet nur an eine Schutzkontaktsteckdose mit
ordnungsgemaeB geerdetem Schutzkontakt anschlieBen.
o Alle angeschlossenen Geraete ebenfalls an
Schutzkontaktsteckdosen mit ordnungsgemaeB geerdetem
Schutzkontakt anschlieBen.

PERICOLO

Per evitare scosse elettriche:

o Il cavo di alimentazione deve essere collegato a una
presa munita di terra di sicurezza e propriamente
cablata.
o Tutte le unita esterne di questo prodotto, devono
essere collegate a prese munite di terra di sicurezza
e propriamente cablate.

Tables xiii

FARE

For a unnga elektrisk stot:

o Nettkabelen ma vaere plugget i en korrekt koblet og
jordet stikkontakt.
o Alt utstyr som er koblet til dette produktet ma vaere
plugget i en korrekt koblet stikkontakt.

PERIGO

Para evitar choques electricos:

o O cabo de alimentacao tem de estar ligado a uma
tomada de corrente correctamente instalada e com
ligacao a terra.
o Todo o equipamento ligado a esta maquina tambem deve
estar ligado a tomadas correctamente instaladas.

PELIGRO

Para evitar peligro de descargas:

o El cable de alimentacion debe estar conectado a una
toma de corriente adecuadamente cableada y con toma
de tierra.
o Cualquier equipo al que se conecte este producto debe
estar tambien conectado a tomas de corriente
adecuadamente cableadas.

VARNING -- LIVSFARA

Foer att undvika elolycksfall:

o Naetkabeln maste anslutas till ett raett kopplat
jordat eluttag.
o Aeven annan utrustning som ska anslutas till den haer
produkten maste anslutas till jordat uttag.

xiv 8224 Ethernet Stackable Hub

DANGER

To avoid a shock hazard, do not connect or disconnect any
cables or perform installation, maintenance, or
reconfiguration of this product during an electrical
storm.

GEVAAR !

Om het gevaar voor elektrische schokken te vermijden, mag
u geen kabels aansluiten of loskoppelen en dit product
niet installeren, onderhouden of opnieuw instellen
tijdens een onweer.

PERIGO

Para evitar perigo de choque, nao conecte ou desconecte
quaisquer cabos ou faca instalacao, manutencao ou
reconfiguracao deste produto durante uma tempestade
magnetica.

FARE!

Undga elektrisk stod:

Produktet ma hverken installeres, vedligeholdes eller
omkonfigureres i tordenvejr. Det samme gaelder for
tilslutning eller afmontering af kabler.

VAARA

Aelae kytke tai irrota kaapeleita aelaekae asenna tai
huolla taetae laitetta tai muuta sen kokoonpanoa
ukonilman aikana. Muutoin voit saada saehkoeiskun.

Tables xv

DANGER

Pour eviter tout risque de choc electrique, ne manipulez
aucun cable et n'effectuez aucune operation
d'installation, d'entretien ou de reconfiguration de ce
produit au cours d'un orage.

VORSICHT

Aus Sicherheitsgruenden bei Gewitter an diesem Geraet
keine Kabel angeschlieBen oder loesen. Ferner keine
Installations-, Wartungs oder Rekonfigurationsarbeiten
durchfuehren.

PERICOLO

Per evitare scosse elettriche, non collegare o scollegare
cavi o effettuare installazioni, riconfigurazioni o
manutenzione di questo prodotto durante un temporale.

FARE

For a unnga elektrisk stot ma ikke kabler kobles til
eller fra. Du ma heller ikke foreta installering,
vedlikehold eller rekonfigurering av dette produktet
under tordenvaer.

PERIGO

Para evitar possiveis choques electricos, nao ligue nem
desligue cabos, nem instale, repare ou reconfigure a
maquina, durante uma trovoada.

xvi 8224 Ethernet Stackable Hub

PELIGRO

Para evitar la posibilidad de descargas, no conecte o
desconecte ningun cable, ni realice ninguna instalacion,
mantenimiento o reconfiguracion de este producto durante
una tormenta electrica.

VARNING -- LIVSFARA

Vid askvaeder ska du aldrig ansluta eller koppla ur
kablar eller arbeta med installation, underhall eller
omkonfigurering av utrustningen.

DANGER

No user serviceable parts inside product. Refer service
to qualified personnel.

DANGER

For 220 volt operation, be sure to use a harmonized
grounded 3 conductor cord, rated 6 Amp minimum, with a
suitable cord for connection to the equipment and
terminating in an IEC approved plug for proper connection
to the branch circuit.

GEVAAR

Dit produkt bevat geen onderdelen die door de gebruiker
kunnen worden hersteld. Voor herstellingen moet u een
beroep doen op gespecialiseerd onderhoudspersoneel.

GEVAAR

Bij gebruik met 220 Volt, moet u een driedradig netsnoer
met aarding gebruiken van minimum 6 Amp, en een geschikte
kabel voor aansluiting op de apparatuur en eindigend in
een stekker die voldoet aan de IEC-normen voor een
correcte aansluiting op de verdeelkast.

Tables xvii

PERIGO

Dentro deste produto nao existem pecas que possam ser
manuseadas por parte do usuario. Qualquer servico dentro
deste produto devera ser executado por pessoa autorizada
e qualificada.

PERIGO

Para operacao em 220 volts, certifique-se de usar um cabo
condutor, aterrado, composto por um conjunto de 3 fios,
com a capacidade minima de 6 amperes, flexivel,
possibilitando a conexao de um lado do cabo ao
equipamento e terminando com um plugue aprovado pelo IEC
para a conexao apropriada do outro lado ao ponto de
forca.

FARE!

Indvendigt eftersyn af dette produkt ma kun foretages af
servicepersonale.

FARE!

Ved tilslutning til 220 V:
Brug kun en 3-polet netledning og et tilsvarende stik,
der opfylder de normale sikkerhedskrav. Af hensyn til
sikkerheden ma stikket kun tilsluttes en stikkontakt, der
har korrekt jordforbindelse.

VAARA

Tuotteessa ei ole kaeyttaejaen huollettavaksi
tarkoitettuja osia. Tuotteen saa huoltaa vain
ammattitaitoinen huoltoedustaja.

xviii 8224 Ethernet Stackable Hub

VAARA

Kun jaennite on 220 volttia, on kaeytettaevae
maadoitettua verkkojohtoa, joka kestaeae vaehintaeaen 6
ampeerin virran. Johdossa on oltava myoes IEC-standardin
mukainen pistoke, jonka avulla johdon voi kytkeae
pistorasiaan.

DANGER

Le produit ne contient pas de pieces reparables par
l'utilisateur. Adressez-vous a du personnel qualifie
pour les reparations.

DANGER

Pour l'utilisation en 220 Volt, veillez a utiliser un
cordon trifilaire avec mise a la terre de minimum 6 Amp,
et un cable permettant la connexion aux appareils et
termine par une prise repondant aux normes IEC pour une
connexion correcte au circuit de branchement.

VORSICHT

Keine vom Benutzer zu wartenden Teile vorhanden.
Instandhaltungsarbeiten duerfen nur von Fachpersonal
durchgefuehrt werden.

VORSICHT

Aus Sicherheitsgruenden liefert IBM zusammen mit diesem
Produkt ein Netzkabel mit geerdetem AnschluBstecker. Nur
von der IBM empfohlene und zugelassene AnschluBkabel
verwenden. Den Stecker des Netzkabels nur an eine
vorschriftsmaeBig geerdete Steckdose anschlieBen.

PERICOLO

Questo prodotto non contiene parti sostituibili
dall'utente. Se occorre, richiedere assistenza tecnica a
personale specializzato.

Tables xix

PERICOLO

Per il funzionamento a 220 V utilizzare un cavo di
alimentazione di tipo armonizzato, trifilare, provvisto
del collegamento alla terra di sicurezza, con portata in
corrente minimo di 6 A, avente un conduttore adatto al
collegamento all'apparecchiatura e terminante con una
spina conforme alle norme CEI per il corretto
collegamento all'impianto elettrico.

FARE

Inneholder ingen deler som kan repareres av brukeren.
Overlat service til kvalifisert personell.

FARE

Hvis nettspenningen er 220 volt, ma du bruke en
harmonisert, jordet kabel med 3 ledere for minst 6
ampere. Kabelen ma ha en passende plugg for utstyret, og
den ma avsluttes i en IEC-godkjent plugg for riktig
tilkobling til nettet.

PERIGO

Nenhum dos componentes internos pode ser reparado pelo
cliente. Para qualquer reparacao, chame sempre um
tecnico especializado.

PERIGO

Para ligacao a uma tensao de 220 Volt, utilize sempre um
cabo de 3 condutores com terra, aprovado, para 6 Ampere
minimo, com um cabo apropriado para ligacao ao
equipamento e que termine com uma ficha aprovada pela
CEI, para obter uma ligacao correcta ao circuito de
derivacao.

xx 8224 Ethernet Stackable Hub

PELIGRO

Dentro del producto no hay piezas a las que el usuario
pueda prestar servicio tecnico. Ceda el servicio a
personal cualificado.

PELIGRO

Para una operacion a 220 voltios, asegurese de utilizar
un cable de 3 patillas con toma de tierra, para un minimo
de 6 Amperios, con un cable adecuado para la conexion al
equipo y que termine en un conector aprobado por la IEC
para la conexion adecuada al circuito.

VARNING

Service ska endast utfoeras av utbildad servicepersonal.

VARNING

Vid anslutning till 220V ska godkaend skyddsjordad
naetkabel anvaendas.

Tables xxi

xxii 8224 Ethernet Stackable Hub

ABOUT THIS MANUAL
_________________

This manual describes the features of the IBM 8224
Ethernet Stackable Hub (8224) and explains how to plan
for 8224s in your new or existing network, how to install
8224s, and how to administer 8224s.

WHO SHOULD READ THIS MANUAL
___________________________

If you are a network planner, a hardware installer, a
network administrator, or a service engineer, this manual
will help you in your work with 8224s.

HOW THIS MANUAL IS ORGANIZED
____________________________

This manual contains the following sections:

o Chapter 1, "Introduction and Planning" describes the
features of the 8224 and provides information you
will need to integrate 8224s into your new or
existing network.

o Chapter 2, "Installing the 8224" provides
step-by-step instructions for installing the 8224.
It also explains how to install the optional media
expansion port module.

o Chapter 3, "8224 Administration" helps you determine
which administrative actions are available to your
8224 setup, and then gives instructions for
performing the actions.

o Chapter 4, "Servicing 8224s" gives the procedure for
hot-swapping 8224s and lists the available
replacement parts.

o Appendix A, "Planning Charts" includes three charts
for your use in planning your Ethernet network.

o Appendix B, "Cable Pinout Diagrams" provides pinout
diagrams for the cables and connectors that the 8224
accepts.

o Appendix C, "Validating IP and Netmask Addresses"
explains how to convert between binary octets and
decimal values and how to logically AND IP addresses
and subnet masks.

o Appendix D, "The IBM 8224 Management Information
Base" lists the IBM 8224 private MIB.

o Appendix F, "Notices and Product Warranty" provides
emissions notices, safety notices, a list of
trademarks, and a statement of warranty.

o Appendix G, "Help and Service Information" gives
steps for troubleshooting and for preparing to make a
call to IBM Service.

xxiv 8224 Ethernet Stackable Hub

TECHNICAL AND PLANNING REFERENCES
_________________________________

You might find these publications helpful in planning
your network or in answering detailed technical
questions.

o Carrier Sense Multiple Access with Collision
____________________________________________
Detection (CSMA/CD) Access Method and Physical Layer
____________________________________________________
Specifications, ANSI/IEEE Standard 802.3
______________

o Commercial Building Telecommunications Cabling
______________________________________________
Standard, ANSI/TIA/EIA Standard 568-A
________

o Commercial Building Standard for Telecommunications
___________________________________________________
Pathways and Spaces, ANSI/EIA/TIA Standard 569
___________________

o Administration Standard for the Telecommunications
__________________________________________________
Infrastructure of Commercial Buildings, ANSI/TIA/EIA
______________________________________
Standard 606

o Grounding and Bonding Requirements for
______________________________________
Telecommunications in Commercial Buildings,
__________________________________________
ANSI/TIA/EIA Standard 607

o Generic Cabling for Customer Premises Cabling,
_____________________________________________
ISO/IEC Draft International Standard 11801.

If you intend to use shielded twisted-pair (STP) cabling,
refer to IBM Cabling System Planning and Installation
____________________________________________
Guide, GA27-3361.
_____

If you intend to use optical fiber cabling, refer to IBM
___
Cabling System Optical Fiber Planning and Installation
______________________________________________________
Guide, GA27-3943.
_____

About This Manual xxv

xxvi 8224 Ethernet Stackable Hub

CHAPTER 1. INTRODUCTION AND PLANNING
_____________________________________

This chapter describes the features of the IBM 8224
Ethernet Stackable Hub (8224) and provides information
you will need to integrate 8224s into your new or
existing network.

THE 8224
________

The 8224 is a stackable Ethernet hub that comes in two
versions: Models 001 and 481, which are unmanaged but
potentially manageable, and Models 002 and 482, which are
manageable and enable management of Models 001 and 481 in
a stack. Models 481 and 482 are functionally identical
to Models 001 and 002 respectively, except for the type
of power input. Models 481 and 482 utilize a -48 V dc
input where Models 001 and 002 utilize 100-240 V ac
input. For the remainder of this document, all
information applicable to Models 001 and 481 will refer
to Model xx1. All information applicable to Models 002
and 482 will refer to Model xx2.

Each permits up to sixteen 10BASE-T connections, with the
option to connect to 10BASE5 (AUI), 10BASE2, 10BASE-FL,
or FOIRL networks using optional media expansion port
modules.

Figure 1-1. Front View of the IBM 8224 Ethernet
Stackable Hub Models xx1 and xx2

A stack is formed when up to ten 8224s are connected
_____
through their hub expansion ports (HEPs). The 8224s need
not be stacked physically atop one another, as long as
the total hub expansion cable length from the first 8224
in a stack to the last is under 76.2 m (250 ft).

A managed stack is made up of any combination of Models
_______
xx2 and xx1. In a managed stack, the hub expansion
cables contain an Ethernet bus and an inter-hub control
bus. The Ethernet bus permits communication between any
pair of attached devices, adding just one repeater hop
between them in most cases (see "Interconnecting 8224s"
on page 1-4 for more detail). The inter-hub control bus
passes management information from 8224 to 8224 in a
channel that is separate from that of the Ethernet bus.

An unmanaged stack is made up of Model xx1s only. In an
_________
unmanaged stack, only the Ethernet bus is active.

All management actions must be done using an SNMP-based
network management application, such as IBM StackWatch
for Windows, the 8224 Application for IBM NetView for
Windows, IBM StackWatch for NetWare Management System
(NMS) or the VT100 terminal interface.

FEATURES

ALL MODELS of the 8224 include these features:

o Sixteen 10BASE-T ports with shielded RJ-45 connectors
that accept unshielded twisted-pair (UTP) category 3,
4, or 5 cabling, 100- or 120-ohm foiled twisted-pair
(FTP) category 5 cabling, or shielded twisted-pair
(STP) type 1, 6, 9, 1A, 6A, or 9A cabling(1)

o Repeating of all Ethernet frame formats

o Auto-partitioning of ports whose attached devices
create excessive collisions

o Protection against jabber, using the IEEE 802.3
Medium Attachment Unit Jabber Lockup Protection
algorithm

o One media expansion port (MEP) that accepts optional
slide-in modules for connecting to 10BASE2 or 10BASE5
(AUI) networks, or an optical fiber module for
connecting to 10BASE-FL or FOIRL networks

o Two hub expansion ports (HEPs) that allow you to
interconnect up to ten 8224s, extending management
and data-movement capability among all of the 8224s

o A serial communications (Com) port, for configuring
the 8224 and upgrading microcode out of band

o LEDs that indicate status and collisions, as well as
link status, activity, and partition status at the
port level

o An Uplink switch that permits cascading hubs using
their 10BASE-T ports without need for a special
crossover cable

o Protection of vital configuration data, such as IP
address and port settings, in nonvolatile random
access memory (NVRAM)

---------------

(1) 120- and 150-ohm cabling must use impedance-matching devices to change
the impedance to 100 ohms.

1-2 8224 Ethernet Stackable Hub

o Parts necessary for mounting the 8224 in an EIA
standard 19-inch rack, on a table top, or on a shelf

The MODEL XX2 provides these additional features to the
entire stack:

o An SNMP agent that provides support for these
Management Information Bases (MIBs)

- RFC 1213 (MIB II)
- RFC 1516 (Ethernet Repeater MIB)
- Novell Repeater MIB
- IBM 8224 private MIB (listed in Appendix D)

o SNMP manageability over IP networks using the
following frame formats:

- Ethernet_II
- 802.2 SNAP

o SNMP manageability over IPX networks using the
following frame formats:

- Ethernet_II
- 802.3 RAW
- 802.2
- 802.2 SNAP

o Manageability using optional applications and
platforms, such as IBM StackWatch for Windows, IBM
StackWatch for NMS, and the 8224 Application for IBM
NetView for Windows

o For IP networks

- SNMP manageability over a Serial Line Internet
Protocol (SLIP) link to the Com port

- Support for the Bootstrap Protocol (BootP) and
Trivial File Transfer Protocol (TFTP), for
configuring and upgrading the microcode of any
8224 over an Ethernet link

- Support for TFTP for upgrading the microcode of
any 8224 in a stack through the Com port

o For IPX networks, Novell Hub Management System (HMS)
compliance

o VT100 Manageability over the

- Ethernet using Telenet/IP protocol
- Com Port using Telenet/SLIP or direct VT100
protocol

Chapter 1. Introduction and Planning 1-3

o Port intrusion protection

INTERCONNECTING TYPICAL ETHERNET HUBS

The best way to appreciate the benefit of stacking hubs
is to examine the method of interconnection used by
simpler Ethernet workgroup hubs, which interconnect by
cascading. Figure 1-2 shows three Ethernet workgroup
_________
hubs labeled A, B, and C. Hubs B and C are cascaded from
Hub A.

Because data sent from the workstation to the server must
pass through three hubs along the way, the server is said
to be three repeater hops(2) from the workstation. If
_____________
there are six ports on Hub A, you can cascade up to four
more hubs from Hub A and still have a maximum of three
repeater hops between any two workstations. A limitation
of cascading, however, is that ports that could be used
to attach workstations are being used to interconnect
hubs.

Figure 1-2. Hubs B and C Are Cascaded from Hub A

INTERCONNECTING 8224S

8224s maximize the number of ports available to end
stations by interconnecting using their HEPs. Up to ten
8224s can be linked through HEPs, and the total hub
expansion cable length from the first to the last 8224 in
a stack can be up to 76.2 m (250 ft).

An example stack of interconnected Model xx1s is shown in
Figure 1-3. Because in this example no Model xx2 is
present, only the Ethernet bus is active inside the hub
expansion cables.

Figure 1-3. A Stack of Four Model xx1s

There are two benefits to using the hub expansion ports
to interconnect 8224s. The maximum number of hops between
any two workstations directly connected to 8224s is kept
at one (or one and one-half, depending on distance), and

---------------

(2) A repeater hop is counted whenever an Ethernet frame passes through a
repeater. The IEEE 802.3 standard specifies that a frame sent from one
workstation to another should not pass through more than four repeaters
on the way to its destination.

1-4 8224 Ethernet Stackable Hub

ports intended for connecting workstations are not being
used for interconnecting 8224s.

Cabling and connector requirements for the hub expansion
ports are given in "Cabling Requirements for Hub
Expansion Ports" on page 1-16.

UNDERSTANDING MANAGED STACKS
____________________________

This section describes how 8224s in a stack communicate
with one another, the effects of segmenting 8224s from a
stack, and how to link segmented 8224s.

INTER-8224 COMMUNICATIONS IN MANAGED STACKS

In a stack with one or more 8224 Model xx2s, an inter-hub
control bus is activated inside the hub expansion cables
in addition to the Ethernet bus. The control bus is used
to pass management information from 8224 to 8224.

Figure 1-4 gives a logical view of the inside of the hub
expansion cable for a managed stack.

Figure 1-4. A Managed Stack of 8224s

Using an SNMP-based management application, you can get
the following information about all 8224s in a stack
while attached to any 8224 in a stack:

o Model number and media expansion port module type
o MAC address
o IP address
o IP subnet mask
o IP default gateway
o Whether the 8224 is segmented from the external
Ethernet bus (see "Segmenting 8224s from a Stack" on
page 1-7)

Using an SNMP-based network manager, you can perform any
of the following actions on any 8224 in a stack while
attached to any 8224 in a stack:

o Set the IP address
o Set the IP subnet mask
o Set the IP default gateway
o Segment the 8224 from the external Ethernet bus or
rejoin the 8224 to the bus (see "Segmenting 8224s
from a Stack" on page 1-7)
o Set the Write Community Name
o Enable or disable write protect
o Reset the 8224, to make the new settings take effect

Chapter 1. Introduction and Planning 1-5

Even if 8224s have been segmented from the Ethernet bus,
the inter-hub control bus allows you to set IP
information and segment 8224s from a stack.

WHY SEGMENT 8224S FROM A STACK?

Three major uses of segmentation are to improve
performance, to troubleshoot, and to isolate groups of
users. This section details those uses. "Segmenting
8224s from a Stack" on page 1-7 explains how segmenting
is controlled.

Improving Performance

An unsegmented stack is a single collision domain. All
devices attached anywhere to an unsegmented stack see all
the Ethernet frames generated anywhere else in the stack.

As network traffic increases, excessive collisions can
cause network performance to slow. You can improve
performance by segmenting any number of 8224s from the
other 8224s in a managed stack. Each segmented 8224 is
its own collision domain as long as it is not linked to
any other 8224s.

To enable segmented 8224s to communicate with the rest of
the stack, interconnect them using a bridge, router, or
Ethernet switch. See "Linking Segmented 8224s" on
page 1-7 for more detail.

Troubleshooting

Segmentation can help you isolate areas of your network
that are experiencing problems. You can segment 8224s
one at a time from the rest of the stack while monitoring
stack performance. This technique can help you localize
a problem area to the devices attached to one 8224.

Isolating User Groups

You might have users in your network who have no need for
connectivity outside their department or workgroup. By
connecting their workstations to one or more segmented
8224s, you can limit their network access while keeping
control of the 8224s.

1-6 8224 Ethernet Stackable Hub

SEGMENTING 8224S FROM A STACK

You can use any SNMP management application to segment an
8224 from a managed stack. Figure 1-5 shows physical and
logical views of a stack from which one 8224 has been
segmented. Notice that even though Hub B has been
logically removed from the Ethernet bus, the inter-hub
control bus remains, permitting the management
information described in "Inter-8224 Communications in
Managed Stacks" on page 1-5 to reach the 8224.

Figure 1-5. Hub B Is Segmented from the External Ethernet Bus

LINKING SEGMENTED 8224S

In order to manage a stack of 8224s:

o The 8224 you want to manage must either be a Model
xx2 or be connected in a stack with a Model xx2, and
___

o There must be an Ethernet link between the 8224 to
which your management workstation is attached and the
8224 you want to manage.

When you segment an 8224 from a stack, you break either
the Ethernet link to that 8224, or, if your management
workstation is attached to that 8224, to the rest of the
stack. You have two choices for re-linking segmented
8224s: cascading or interconnecting using a bridge,
router, or Ethernet switch.

To cascade, two or more 8224s must be segmented. When
you cascade 8224s, they can communicate with one another
in one collision domain, but not with the rest of the
stack.

If you interconnect the segmented 8224 or 8224s with the
rest of the stack using a bridge, router, or Ethernet
switch, they can communicate with the other 8224s and
remain independent collision domains. The next two
sections explain these options in detail.

Cascading Segmented 8224s

If more than one 8224 has been segmented, you can cascade
them. Figure 1-6 on page 1-8 shows a stack in which Hubs
B and C have been segmented from the external Ethernet
bus. Hub C is cascaded from port 16 of Hub B, and Hub
B's Uplink switch is set to = (straight-through). Hubs B

Chapter 1. Introduction and Planning 1-7

and C make up one collision domain, and Hubs A and D make
up another.

Within each collision domain, all devices attached to
either hub see all the frames generated by stations
attached to the other hub. Yet Hubs B and C have no path
to enable them to communicate with Hubs A and D.

Figure 1-6. Hub C Is Cascaded from Hub B

If you want to cascade, the 8224 provides a convenient
way to do so without the need for special crossover
cables. You can turn the switch beside port 16 to =
(straight-through), and then use a standard Ethernet
(straight-through) cable to interconnect the hubs.

For more information on situations that require
crossover, see "Straight-Through or Crossover Cables?" on
page 1-15.

Interconnecting Segmented 8224s Using Other Devices

By interconnecting up to ten 8224s in a stack, using
bridges, routers, or Ethernet switches, you can keep
_______ _______ _________________
8224s in separate collision domains and ensure that there
are Ethernet links among them. Figure 1-7 shows Hub C
segmented from the Ethernet bus but linked to the stack
through the switch. The switch connection links Hub C to
the rest of the stack while keeping Hub C in a separate
collision domain.

Figure 1-7. Hub C Is Segmented but Manageable through the Switch

1-8 8224 Ethernet Stackable Hub

ASSIGNING BACKUP PORTS
______________________

A managed stack provides the option of making redundant
connections to network-critical devices, such as servers
or LAN switches. Any port in an 8224, including the
media expansion port, can be used as a backup for any
other port in the same hub only. Figure 1-8 shows an
____________________
example of such a redundant connection. Note that you
must establish two physical connections to the desired
device.

For 10BASE-T ports and for the optical fiber media
expansion port module, a backup port takes over for a
primary port if the primary port loses link test or if
the primary port is auto-partitioned. For the 10BASE2
and 10BASE5 media expansion ports, the backup port takes
over if the primary port is auto-partitioned (10BASE2 and
10BASE5 technologies cannot provide link test).

Figure 1-8. Backup Connection from Hub C to a LAN Switch

You can use any SNMP-based network management application
to assign backup ports.

ETHERNET PLANNING
_________________

The size of each Ethernet collision domain you create is
restricted by these factors:

o The limit of four repeaters between any two devices
in one collision domain

o The cable length restrictions unique to each type of
segment (that is, for 10BASE-T, 10BASE2, and so on)

o If you will use optical fiber links:

- The limit of 4200 m (13 780 ft) between any two
devices in one collision domain

- The optical fiber power budget

These factors are explained in detail in the next four
sections.

Chapter 1. Introduction and Planning 1-9

FOUR-REPEATER LIMIT

The IEEE 802.3 Ethernet standard specifies that a maximum
of four repeaters can be placed in the path between any
two devices in one collision domain.

Count a stack as one repeater hop as long as the total
hub expansion cable length is less than 45.7 m (150 ft).
If the total hub expansion cable length is between 45.7 m
(150 ft) and 76.2 m (250 ft), count a stack as one and
one-half repeater hops.

NOTE: There might be more than four repeaters within a
collision domain, as long as there are no more than four
repeaters in the path between any two devices in the
__________________________________________
collision domain.
________________

MAXIMUM SEGMENT LENGTHS

An Ethernet segment is the total length of cable between
either two repeaters or between a repeater and an
attached device. The different types of Ethernet
supported by the 8224 place different limitations on
segment lengths.

+-------------------------------------------------------+
| Table 1-1. Maximum Segment Lengths for the Supported |
| Ethernet Types |
+------------------+------------------------------------+
| ETHERNET TYPE | MAXIMUM SEGMENT LENGTH |
+------------------+------------------------------------+
| 10BASE-T | 100 m (328 ft) |
+------------------+------------------------------------+
| 10BASE2 | 185 m (607 ft) |
+------------------+------------------------------------+
| AUI | 50 m (164 ft) |
+------------------+------------------------------------+
| FOIRL | 1000 m (3281 ft) |
+------------------+------------------------------------+
| 10BASE-FL | 2000 m (6562 ft) |
+------------------+------------------------------------+

MAXIMUM DISTANCE LIMIT (OPTICAL FIBER ONLY)

A maximum distance limit of 4200 m (13 780 ft) between
any two devices in a collision domain is recommended, to
ensure that there is sufficient time for any transmitting
device to detect a collision before it stops
transmitting. The limit of 4200 m (13 780 ft) applies to
the sum of the cable lengths and the equivalent
__________
distances, added by intervening devices, between the most
_________
widely separated devices in the collision domain.

1-10 8224 Ethernet Stackable Hub

Calculate your network's maximum distance if you are
using optical fiber cabling. Add all the lengths of
cable between the two most widely separated devices in
the collision domain. Count 1 m (3.38 ft) of optical
fiber and 1 m (3.38 ft) of copper cable as equivalent.
The distances you calculate will be slightly
conservative.

Also, intervening devices introduce delays that can be
converted to equivalent distances of cable. In
Table 1-2, equivalent distances for signals passing
through an 8224 are given. Add the equivalent distances
to the total cable lengths, and then compare the result
to the 4200 m (13 780 ft) limit.

NOTE: It is beyond the scope of this manual to give
equivalent distances for every device that could be in a
path between two devices in a collision domain. Refer to
the documentation for each device in the path to
determine the delay. One microsecond (&mu.s) of delay is
equivalent to 200 m (656 ft) of cable.

+-------------------------------------------------------+
| Table 1-2. Equivalent Distances for Signals Passing |
| Through an 8224 |
+--------------------+----------------------------------+
| | SIGNAL OUT |
| +------+------+------+------+------+
| | | | | OPTIC|L |
| SIGNAL IN | 10BAS|-10BAS|2AUI | FIBER| HEP |
+--------------------+------+------+------+------+------+
| 10BASE-T | 183 | 176 | 128 | 174 | 210 |
| | m | m | m | m | m |
| | (600 |t(577 |t(420 |t(571 |t(689 |t)
+--------------------+------+------+------+------+------+
| 10BASE2 | 188 | N/A | N/A | N/A | 222 |
| | m | | | | m |
| | (617 |t) | | | (728 |t)
+--------------------+------+------+------+------+------+
| AUI | 134 | N/A | N/A | N/A | 166 |
| | m | | | | m |
| | (440 |t) | | | (545 |t)
+--------------------+------+------+------+------+------+
| HEP | 164 | 242 | 200 | 210 | N/A |
| | m | m | m | m | |
| | (538 |t(794 |t(656 |t(689 |t) |
+--------------------+------+------+------+------+------+
| OPTICAL FIBER | 240 | N/A | N/A | N/A | 270 |
| (10BASE-FL or | m | | | | m |
| FOIRL) | (787 |t) | | | (886 |t)
+--------------------+------+------+------+------+------+

Chapter 1. Introduction and Planning 1-11

Example: Calculating the Maximum Distance Limit

The workstations in Figure 1-9 are the most widely
separated in this network. Calculate the maximum length
of optical fiber cable allowable between them.

Figure 1-9. An Example Network with an Optical Fiber
Link

Add all of the known cable lengths and equivalent
distances for port-to-port transitions.

NOTE: Although there can be up to ten 8224s in a stack,
a signal that goes into and out of the same HEP on a
single 8224, is not affected by that hub. It is only
necessary to consider the actual cable length between the
HEPs.

+-----------------------------------------------+--------+
| Left workstation-to-8224 cable | 75 m |
+-----------------------------------------------+--------+
| 10BASE-T-to-HEP equivalent distance | 210 m |
+-----------------------------------------------+--------+
| HEP-to-HEP cable | 10 m |
+-----------------------------------------------+--------+
| HEP-to-optical fiber equivalent distance | 210 m |
+-----------------------------------------------+--------+
| Optical fiber-to-HEP equivalent distance | 270 m |
+-----------------------------------------------+--------+
| HEP-to-HEP cable (two 1-m segments) | 2 m |
+-----------------------------------------------+--------+
| HEP-to-10BASE2 equivalent distance | 242 m |
+-----------------------------------------------+--------+
| 8224-to-right workstation cable | 100 m |
+-----------------------------------------------+--------+
| Total | 1119 m |
+-----------------------------------------------+--------+

Using the maximum allowable distance of 4200 m (13 780
ft), the maximum allowable length of the optical fiber
cable is:

4200 m - 1119 m = 3081 m (10 108 ft)

In this example, a 2000-m (6562-ft) 10BASE-FL segment
does not seem to exceed the maximum distance limit.

To be sure, you must calculate the maximum distance in
reverse as well, because the port-to-port equivalent
distances might be different. For this example, the
distances in reverse total 1053 m (3455 ft). The maximum
distance limit, in reverse, is 3147 m (10 325 ft).

1-12 8224 Ethernet Stackable Hub

Before you conclude that the cable length is completely
acceptable, check the power loss budget for your optical
fiber cabling. See "Example: Power Loss Budgeting" on
page 1-14.

POWER LOSS BUDGETING (OPTICAL FIBER ONLY)

Optical fiber links are subject to power loss
restrictions in addition to distance restrictions. The
important consideration is whether the signal will be
strong enough when it reaches the receiver that no data
has been lost in the transmission.

To determine whether the signal will be strong enough at
the receiver, you need three pieces of information:

o Transmission power
o Power loss during transmission
o Minimum receiver sensitivity

Transmission power results from a combination of the
transmitter's power and the gauge of optical fiber used.
Transmission power and minimum receiver sensitivity are
fixed values that depend on the gauge of the cable.

The difference between transmission power and minimum
receiver sensitivity is the power budget. The power
budget tells how much power loss is allowable during
transmission.

+-------------------------------------------------------+
| Table 1-3. 8224 Optical Fiber MEP Power Budgets |
+-------------+-------------+-------------+-------------+
| OPTICAL | | MINIMUM | |
| FIBER | TRANSMISSION| RECEIVER | POWER |
| CABLE GAUGE | POWER | SENSITIVITY | BUDGET |
+-------------+-------------+-------------+-------------+
| 62.5/125 | | | |
| &mu.m | -19.5 dB | -32.5 dB | 13.0 dB |
+-------------+-------------+-------------+-------------+
| 50/125 | | | |
| &mu.m | -23.3 dB | -32.5 dB | 9.2 dB |
+-------------+-------------+-------------+-------------+
| 100/140 | | | |
| &mu.m | -14.0 dB | -32.5 dB | 18.5 dB |
+-------------+-------------+-------------+-------------+

Power loss occurs wherever there is an interruption in
the optical fiber, for instance, at a patch panel or
splice, and it occurs gradually as a signal travels
through a cable.

Chapter 1. Introduction and Planning 1-13

Different brands of cables, splices, and patch panels
have different power loss characteristics. Refer to the
manufacturer's documentation for power loss values for
each component in the path between the two devices. For
splices and patch panels, loss is expressed in decibels
(dB). For cables, loss is expressed in decibels per
kilometer (dB/km).

Given a power budget (p dB), a total of losses due to
_
intervening devices such as patch panels and splices (i
_
dB), and a loss per unit of cable (c dB/km), you can
_
calculate the maximum cable length your power budget
allows (m km) by using this formula:
_

m = p dB - i dB
___________
c dB/km

Example: Power Loss Budgeting

In the previous example (see Figure 1-9 on page 1-12),
the cable gauge was 62.5/125 &mu.m. Because there is an
8224 at each end of the optical fiber cable, the
transmission power and minimum receiver sensitivity are
known and are given in Table 1-3 on page 1-13.

In this example, the power budget (p) is 13 dB. If there
_
are two patch panels in the path between the two 8224s,
each of which loses 0.5 dB, one splice, which loses 0.4
dB, and the cable itself, which loses 4 dB/km, you can
calculate the maximum permissible length (m) of optical
_
fiber between the two points.

m = 13 dB - 1.4 dB
______________
4.5 dB/km

m = 11.6 dB
_______
4.5 dB/km

m = 2.58 km

The power loss budget allows 2580 m (8465 ft) between the
optical fiber ports. You can safely exceed the 2000 m
(6562 ft) maximum segment length for 10BASE-FL by 580 m
(1903 ft).

1-14 8224 Ethernet Stackable Hub

CABLES AND CONNECTORS
_____________________

Cable and connector requirements differ depending on the
port to which each cable connects.

CABLING REQUIREMENTS FOR 10BASE-T PORTS

The sixteen 10BASE-T ports in the 8224 accept either
100-ohm UTP category 3, 4, or 5 cables, 100- or 120-ohm
FTP category 5 cables, or 150-ohm IBM STP type 1, 6, 9,
1A, 6A, or 9A cables. UTP and FTP cables must use RJ-45
connectors; STP cables must use cable adapters to convert
to RJ-45 connectors. See "RJ-45 Auto-polarity Reversal"
on page 3-50 for information on the RJ-45 Auto-polarity
Reversal feature.

Figure 1-10. RJ-45 Connector for 10BASE-T

Token-ring STP cables will not work as-is in Ethernet
environments, because the wires pin out to the connectors
differently. You can adapt the connectors; see
Figure B-3 on page B-1 for the correct pinout for
Ethernet.

At end stations and at the 8224, you will also need
impedance-matching devices to change the impedance of
150-ohm STP and 120-ohm FTP to 100 ohms. Changing the
impedance does not reduce maximum drive distances.

Whether UTP, FTP, or STP, all cables and connectors you
use should meet Commercial Building Telecommunications
Cabling Standard ANSI/TIA/EIA 568-A,

Straight-Through or Crossover Cables?

Use straight-through cables to make 10BASE-T connections
_______________________
to devices such as workstations and servers.

Crossover cables are typically required when making
________________
10BASE-T connections to other hubs. The 8224, however,
offers a way to bypass this requirement. If the
connection is to a different hub, use 8224 port 16 and
turn the uplink switch beside it to = (straight-through).
This action permits the use of a straight-through cable
for connections that usually require crossover cables.

If you find that you need a crossover cable, you can make
one yourself from a straight-through cable. Pinout
diagrams are given in "Crossover 10BASE-T Cables" on
page B-1.

Chapter 1. Introduction and Planning 1-15

CABLING REQUIREMENTS FOR MEDIA EXPANSION PORTS

Cable and connector requirements differ depending on the
MEP module you use.

AUI Port Module

The AUI port is a standard, DB-15 female connector. You
can connect either an AUI cable or a transceiver to it.

10BASE2 Port Module

Use standard, thin coaxial cable with a BNC connector.

FOIRL/10BASE-FL Port Module

Use either 62.5/125 &mu.m, 50/125 &mu.m, or 100/140 &mu.m
optical fiber cable with ST connectors.

CABLING REQUIREMENTS FOR HUB EXPANSION PORTS

Use standard four-pair cables, such as UTP category 3, 4,
or 5, to interconnect 8224s through their HEPs. All HEP
cables must have RJ-45 connectors. The wire pairs should
be arranged as shown in Figure B-7 on page B-2 or
Figure B-8 on page B-2.

One 152.4-mm (6-in.) hub expansion cable is shipped with
every 8224. If you need longer cables to interconnect
your 8224s, remember that the total cable length from the
first 8224 to the last 8224 in the stack must not exceed
76.2 m (250 ft).

CABLING REQUIREMENTS FOR THE COM PORT

The Com port is a standard DB-9 male connector, which
provides a standard EIA/TIA-232-E (was RS-232-C) serial
interface. You can connect locally, with a null-modem
cable, or remotely, using a serial cable and a modem at
each end, and telephone lines in between. Once
connected, you can manage the 8224 and upgrade microcode.

You can make a null-modem cable by connecting a
null-modem adapter to a standard serial cable.

1-16 8224 Ethernet Stackable Hub

PROTECTED VITAL CONFIGURATION DATA
__________________________________

The following configuration information is stored in
nonvolatile memory (NVRAM) and will survive a power
outage:

o System name and location
o IP address
o IP subnet mask
o IP default gateway
o Write community name
o Write-protect setting
o Authentication trap setting
o Trap tables for IP and IPX
o Routing information
o Backup port settings
o Com port's IP address
o Com port's subnet mask
o Whether ports are enabled or disabled
o Whether link test is enabled or disabled
o Whether BootP/RARP requests are enabled or disabled
o Whether the 8224 is segmented from the external
Ethernet bus
o Whether auto-discovery is enabled or disabled
o Whether port intrusion protection is enabled or not,
and the passwords

These settings are retained in both Models xx1 and xx2,
but are relevant only to managed 8224s (that is, a Model
xx2 or xx1 connected in a stack with a Model xx2).

POWER REQUIREMENTS AND CHARACTERISTICS
______________________________________

The power inlet connectors are on the back of the 8224.

AC POWER INPUT

The 8224 Models 001 and 002 have internal, auto-ranging
power supplies that adapt to voltages between 100 and 240
V ac at frequencies of 50 to 60 Hz.

Following are characteristics of the 8224 AC power
supply:

POWER USAGE (MAXIMUM) 30 W (102 BTU per hour)
LINE CURRENT (MAXIMUM) 0.5 A at 120 V ac; 0.25 A at 240
V ac
LINE CURRENT (TYPICAL) 0.25 A at 120 V ac; 0.18 A at
240 V ac
KVA (WORST CASE) 0.05 kVA
KVA (TYPICAL) 0.03 kVA at 120 V ac; 0.04 kVA
at 240 V ac

Chapter 1. Introduction and Planning 1-17

DC POWER INPUT

The 8224 Models 481 and 482 have internal power supplies
that accept -48 V dc. This power supply is provided in
order to make the 8224 compatible with the Network
Equipment Building System (NEBS) standards for equipment
used by the telephone industry.

CAUTION:
WHEN INSTALLING THE 8224 MODEL 481 OR MODEL 482, CONNECT
THE EQUIPMENT TO A 48 V DC SUPPLY SOURCE THAT IS
ELECTRICALLY ISOLATED FROM ANY AC SOURCE. THE 48 V DC
SOURCE MUST BE RELIABLY GROUNDED.

CAUTION:
THE 8224 MODELS 481 AND 482 ARE TO BE INSTALLED ONLY IN
RESTRICTED ACCESS AREAS (DEDICATED EQUIPMENT ROOMS,
EQUIPMENT CLOSETS, OR THE LIKE) IN ACCORDANCE WITH
ARTICLES 110-16, 110-17, AND 110-18 OF THE NATIONAL
ELECTRIC CODE, ANSI/NFPA 70.

Following are characteristics of the 8224 DC power
supply:

POWER USAGE (MAXIMUM) 30 W
LINE CURRENT (MAXIMUM) 0.8 A at -48 V dc

1-18 8224 Ethernet Stackable Hub

PHYSICAL CHARACTERISTICS
________________________

This section gives the dimensions and weight of an 8224.

WIDTH 440 mm (17.32 in.)
DEPTH 264 mm (10.4 in.)
HEIGHT (WITHOUT FEET) 43.7 mm (1.7 in.)
HEIGHT (WITH FEET) 46.8 mm (1.84 in.)
WEIGHT: 001 AND 002 3.1 kg (6.9 lb)
WEIGHT: 481 AND 482 2.9 kg (6.5 lb)

OPERATING ENVIRONMENT
_____________________

This section specifies the physical environment you
should provide for 8224s.

SPACE REQUIREMENTS

If you will link multiple 8224s in a stack, be sure that
you have enough space available in your rack or shelf for
the number of hubs that will be stacked together. If you
have insufficient space to stack all the 8224s together,
you can place them side-by-side or on separate shelves or
racks. Just remember that the maximum combined length
for all the expansion cables in one stack is 76.2 m (250
ft).

If you plan to rack-mount your 8224, do not attach the
rubber feet to its underside, or the 8224 will exceed
standard height.

Allow at least 51 mm (2 in.) at the sides and back of the
8224 for air circulation and cable connections. Leave
additional space in front for viewing the LEDs.

ENVIRONMENTAL REQUIREMENTS

POWER-ON TEMPERATURE 10&degree.-40&degree.C
(50&degree.-104&degree.F)
POWER-OFF TEMPERATURE 10&degree.-52&degree.C
(50&degree.-125&degree.F)
RELATIVE HUMIDITY 8%-80%
STORAGE TEMPERATURE 1&degree.-60&degree.C
(33&degree.-212&degree.F)

Chapter 1. Introduction and Planning 1-19

ACOUSTIC CHARACTERISTICS
________________________

Table 1-4 is a declaration of the 8224's noise emission
characteristics.

+---------------------------------------------------------------------------+
| Table 1-4. Noise Emission Characteristics of the 8224 |
+---------+---------------+----------------+----------------+---------------+
| | | LÕWAdþ | LÕpAmþ | <LÕpAþ>Õmþ |
| Type | Description +--------+-------+-------+--------+-------+-------+
| | | Operati|gIdling| Operat|nIdling | Operat|nIdling|
| | | (bels) | (bels)| (dB) | (dB) | (dB) | (dB) |
+---------+---------------+--------+-------+-------+--------+-------+-------+
| 8224--xx| Ethernet | | | | | | |
| 8224--xx| Stackable | 4.9 | 4.9 | N/A | N/A | 34 | 34 |
| | Hub | | | | | | |
+---------+---------------+--------+-------+-------+--------+-------+-------+
| |
+---------------------------------------------------------------------------+
| Notes: |
+---------------------------------------------------------------------------+
| |
+---------------------------------------------------------------------------+
| LÕWAdþ is the declared (upper limit) sound power level for a random |
| sample of machines. |
| |
| LÕpAmþ is the mean value of the A-weighted sound pressure levels at |
| the operator position (if any) for a random sample of machines. |
| |
| <LÕpAþ>Õmþ is the mean value of the A-weighted sound pressure levels at |
| the one-meter (bystander) positions for a random sample of |
| machines. |
| |
| N/A Indicates "not applicable" (that is, having no defined operator |
| position.) |
+---------------------------------------------------------------------------+
| |
+---------------------------------------------------------------------------+
| All measurements were made in accordance with ANSI S12.10 and reported in |
| conformance with ISO DIS 9296. |
+---------------------------------------------------------------------------+
| |
+---------------------------------------------------------------------------+

FILLING OUT THE PLANNING CHARTS
_______________________________

Planning charts are provided in Appendix A, "Planning
Charts." They are:

o Rack Inventory Chart
o IBM 8224 Stack Chart
o IBM 8224 Setup and Cabling Chart.

1-20 8224 Ethernet Stackable Hub

You are encouraged to make as many copies of these charts
as you need.

Depending upon the size and complexity of your network,
you might not need to use all of the charts provided.
However, the IBM 8224 Setup and Cabling Chart is useful
for even the smallest LAN segment.

FILLING OUT THE RACK INVENTORY CHART

The Rack Inventory Chart allows you to keep track of all
components installed in each rack in your establishment.
In larger organizations, this chart is particularly
useful.

Create a Rack Inventory Chart for each of the racks where
you will be installing components. Mark the location of
each component on the Rack Inventory Charts using the
scaled template provided in the back of this manual.
Write a unit number and device type for each component on
the Rack Inventory Chart.

FILLING OUT THE IBM 8224 STACK CHART

The IBM 8224 Stack Chart is intended both as a planning
tool and as a record of device locations. Use it in
planning to make sure that the total length of the all
the hub expansion cables in a stack does not exceed 76.2
m (250 ft). Then, keep it as a record of which network
address (IP or IPX) and locally administered address you
have assigned to each 8224 and of where each 8224 is
located.

FILLING OUT THE IBM 8224 SETUP AND CABLING CHART

Use the IBM 8224 Setup and Cabling Chart to explain to
the installer how and where to mount the 8224 and how to
connect the appropriate cables to it. Keep a copy for
your records.

Fill out the Building and Location blanks with enough
information for the installer to find the place to
install the 8224. Write the 8224's MAC address in the
blank provided. (You can find the MAC address of each
8224 printed on the label just above the Com port.) Add
the Segment, Unit Number, and IP or IPX Address.

In the Media Expansion Port (MEP) section, mark whether
an AUI, a 10BASE2, or an FOIRL/10BASE-FL port module
should be installed, or none at all.

Chapter 1. Introduction and Planning 1-21

For each port, write an identifier for the device at the
other end of the cable. Include such information as the
device's MAC address and location. In the Connect To:
section, write the identifier for the port to which the
installer should connect the cable from the 8224's port
(if cable will not connect directly to the device.) For
example, if the 8224 is to be installed in a wiring
closet, you will probably indicate that the installer
should connect a patch cable from a port in the 8224 to a
port in a patch panel.

Use the Uplink Switch (port 16) section to indicate to
the installer how the switch should be set.

Use the Hub Expansion Ports section to tell the installer
which 8224s to connect and where to find the other 8224s,
since they can be in different locations.

1-22 8224 Ethernet Stackable Hub

CHAPTER 2. INSTALLING THE 8224
_______________________________

This chapter provides step-by-step instructions for
installing the 8224. It also explains how to install the
optional media expansion port module.

BEFORE YOU BEGIN
________________

1. EXAMINE THE CONTENTS OF THE PACKAGE.

Figure 2-1. Contents of the 8224 Package

Along with this manual, the 8224 package should
contain:

o The 8224 with mounting brackets attached
o A cable management bracket
o Four self-adhesive rubber feet for
surface-mounting
o One 152.4-mm (6-in.) hub expansion cable
o A power cord (Models 001 and 002 only)

If any item is missing or damaged, contact your place
of purchase.

2. GATHER THE OTHER MATERIALS YOU WILL NEED:

o The Rack Inventory Chart, the IBM 8224 Stack
Chart, and the IBM 8224 Setup and Cabling Chart,
which tell you where to install the 8224 and
which cables to connect
o If you will be installing a media expansion port
module (see "Installing a Media Expansion Port
Module" on page 2-4), a small, flat-blade
screwdriver
o And, if you will be rack-mounting the 8224
- Two rack-mounting screws that are appropriate
for your rack
- A screwdriver that is appropriate for your
rack-mounting screws

SETUP
_____

Look at the Setup and Cabling Chart for instructions
about whether to rack-mount or surface-mount the 8224.

RACK-MOUNTING THE 8224

NOTES:

1. Do not attach the rubber feet if you are
rack-mounting the 8224. With the feet attached, the
8224 exceeds 1 unit of standard rack-mount height
(1-3/4 in.).

2. If you are mounting a Model 481 or 482, refer to
"Special Mounting Brackets for Models 481 and 482" on
page 2-3 for information concerning special mounting
brackets available for these models.

1. Using a screwdriver, remove the four screws (two on
each side) that attach the mounting brackets to the
sides of the 8224 as shown in Figure 2-2.

NOTE: Do not remove the middle screw that is
accessible through the hole in the bracket. This
screw does not attach the bracket.

2. Rotate the brackets and reattach them as shown in
Figure 2-2.

Figure 2-2. Rotating the Rack-Mounting Brackets

3. Look at the Rack Inventory Chart and the IBM 8224
Stack Chart to determine where in the rack to mount
the 8224.

4. Gather the rack-mounting screws (not provided) and
the cable management bracket and place them within
reach.

5. Hold the 8224 in position in the rack and start the
screw that will secure the left bracket.
____

6. On the right side, line up the holes of the rack, the
_____
mounting bracket, and the cable management bracket,
and then start the screw, as shown in Figure 2-3.

Figure 2-3. Attaching the Cable Management Bracket

2-2 8224 Ethernet Stackable Hub

7. Tighten the screws on each side, and then continue
with the instructions under "Installing a Media
Expansion Port Module" on page 2-4.

Special Mounting Brackets for Models 481 and 482

Special mounting brackets are available for Models 481
and 482. These brackets provide increased protection for
the 8224 in case of severe shock to the support
structure.

The brackets are provided in the following mounting kits:

P/N 38H6969 for 19-in. equipment racks
P/N 38H6970 for 23-in. equipment racks

Each kit must be ordered separately. Figure 2-4
illustrates the mounting method for both kits.

Figure 2-4. Special Mounting Brackets for Models 481 and
482.

For more information about ordering these kits, contact
your local IBM marketing representative or your local IBM
authorized remarketer.

Chapter 2. Installing the 8224 2-3

SURFACE-MOUNTING THE 8224

1. Remove the four rubber feet from their packaging,
remove the paper backing from each, and press each in
place on the bottom corners of the 8224.

2. Turn the 8224 over and place it on the surface where
it will be used.

3. Continue with the instructions under "Installing a
Media Expansion Port Module."

INSTALLING A MEDIA EXPANSION PORT MODULE
________________________________________

Media expansion port modules are optional. From the
front, they appear as in Figure 2-5. If you have one to
install, follow the steps below. If not, go to
"Connecting Cables" on page 2-5.

Figure 2-5. Front Views of the Media Expansion Port
Modules

1. Make sure that the power to the 8224 is OFF.

2. Using a small, flat-blade screwdriver, remove the two
screws that hold the plate marked Media Expansion
_______________
Port. Remove the plate and save the screws. Set the
____
plate aside.

Figure 2-6. Location of the Media Expansion Port

3. Before you open the protective bag that contains the
media expansion port module, touch the bag to the
front cover of the 8224 to discharge any static
electricity that could damage the module.

4. Remove the module from its protective bag.

5. Insert the module into the opening as shown in
Figure 2-7.

NOTE: Be careful to hold the module absolutely level
________________
as you insert it into the opening. It is possible to
seat the module above the connector and have the
connection still look and feel secure.

Figure 2-7. Inserting a Media Expansion Port Module

2-4 8224 Ethernet Stackable Hub

CONNECTING CABLES
_________________

Remember these tips when connecting cables:

o Avoid stretching or bending the cables.

o Avoid routing the cables near potential sources of
electromagnetic interference, such as motorized
devices or fluorescent lights.

o Route cables away from aisles and walkways to avoid
creating trip hazards. Use floor cable covers to
secure cables if such routes cannot be avoided.

CONNECTING A CABLE TO THE MEDIA EXPANSION PORT

AUI Port

1. Open the latch by sliding it to the right.

2. Connect either an AUI cable or a transceiver (neither
is provided) to the AUI port.

3. Secure the cable or transceiver by sliding the latch
to the left. Use the blade of a screwdriver if you
have trouble reaching the latch.

4. Thread the cable through the cable management bracket
so that it does not block the LEDs on the front of
the 8224.

5. Continue with "Connecting Cables."

10BASE2 Port

1. Seat the connector with a half twist clockwise.

2. Thread the cable through the cable management bracket
so that it does not block the LEDs on the front of
the 8224.

3. Continue with "Connecting Cables."

Chapter 2. Installing the 8224 2-5

FOIRL/10BASE-FL Port

1. Seat each twin connector with a half twist clockwise.

2. Thread the cable through the cable management bracket
so that it does not block the LEDs on the front of
the 8224.

3. Continue with "Connecting Cables" on page 2-5.

CONNECTING CABLES TO 10BASE-T PORTS

NOTE: Follow your organization's procedures for cable
labeling, if they exist. If not, we suggest you write on
the label a unique identifier for the cable, the location
and MAC address of the device at the other end of the
cable, and the number of the port to which the device is
attached.

1. Look at the IBM 8224 Setup and Cabling Chart to
determine which cables should be connected to which
of the 8224's ports.

2. Connect the cables, with any transceivers or
impedance-matching devices (baluns) to the
appropriate ports.

3. Label the cables so that it will be easier to find
the device at the other end of the cable if you have
to troubleshoot a network problem.

4. At the attached device's end of each cable, connect a
cable from the device to the faceplate. Connect any
transceivers or impedance-matching devices (baluns)
outside the faceplate.
_______

5. Label the cables so that it will be easier to find
the device at the other end of the cable if you have
to troubleshoot a network problem.

Setting the Uplink Switch

1. Look at the IBM 8224 Setup and Cabling Chart to
determine how to set the Uplink Switch.

2. If you need to turn the switch, use a 3-mm (1/8-in.)
flat-blade screwdriver to do so.

Figure 2-8. Location of the Uplink Switch

2-6 8224 Ethernet Stackable Hub

3. Continue with "Connecting Cables to the Hub Expansion
Ports" on page 2-7, if you are connecting more than
one 8224. Otherwise, go to "Connecting a Modem or a
Null-Modem Cable to the Com Port" on page 2-7.

CONNECTING CABLES TO THE HUB EXPANSION PORTS

1. Look at the IBM 8224 Setup and Cabling Chart and the
IBM 8224 Stack Chart to determine which HEPs to
connect.

2. Make sure that you are using the correct Hub
Expansion cable type.

Refer to "Hub Expansion Cable" on page B-2 for
diagrams.

3. Connect the cables as indicated in the IBM 8224 Setup
and Cabling Chart.

NOTE: Plug the connector into the In port on an 8224
__
before you plug into the Out port on another 8224.
___
Plugging into the Out port first might cause
___
interference on the network.

4. Continue with "Connecting a Modem or a Null-Modem
Cable to the Com Port."

CONNECTING A MODEM OR A NULL-MODEM CABLE TO THE COM PORT

If you have a modem or a null-modem cable to install,
follow the steps in this section. If not, go to
"Switching On the 8224" on page 2-10.

1. If you are using a modem, install it according to the
manufacturer's instructions, then set it to force the
Data Terminal Ready (DTR) signal. This is done by
setting a switch on the modem or by issuing software
commands using the communication program. Refer to
the documentation that came with your modem for
specific instructions.

2. Connect one end of the serial cable or one end of the
null-modem cable to the port labeled Com Port.
________

Figure 2-9. Location of the Com Port

Chapter 2. Installing the 8224 2-7

3. If you are installing a modem, connect the other end
of the cable to the modem. If you are installing a
null-modem cable, connect the other end of the cable
to the Com port on your PC.

4. Continue with "Switching On the 8224" on page 2-10.

CONNECTING POWER TO THE 8224
____________________________

If you are installing Models 001 or 002 continue with "AC
Power." If you are installing Models 481 or 482 go to "DC
Power" on page 2-9.

AC POWER

1. Connect the ac power cord to the power inlet
connector at the rear of the 8224 Models 001 or 002,
as shown in Figure 2-10.

2. Plug the power cord into a live ac outlet.

3. Continue with "Switching On the 8224" on page 2-10.

Figure 2-10. Connecting the AC Power Cord to Models 001
or 002

2-8 8224 Ethernet Stackable Hub

DC POWER

1. Remove the cover from the power terminal block
located on the rear of the 8224 Model 481 or 482.
See Figure 2-11.

Figure 2-11. Rear View of the 8224 Model 481 or 482.

2. Connect - 48 V dc power to the terminals as shown in
Figure 2-12. The terminals labeled A are for
connection to the primary power source. The
terminals labeled B are for connection to an optional
backup power source. In both cases, connect -48 V
power to the terminal labeled -48 and -48 V return to
the terminal labeled RTN.

Figure 2-12. DC Power Terminal Block on the 8224 Model
481 or 482

3. Replace the terminal block cover.

4. Continue with "Switching On the 8224" on page 2-10.

Chapter 2. Installing the 8224 2-9

SWITCHING ON THE 8224
_____________________

This section describes how you should expect the LEDs to
function when you switch the 8224 ON.

1. Switch the 8224 ON.

2. Look for the following LED blink sequence:

o First, the 10BASE-T port LEDs should blink in
patterns of green and then orange (for 5
seconds).

o Then, the LEDs beside the media expansion port
should blink green and then orange (for 2
seconds).

o Then, the OK LED should turn orange (for 30
seconds)

o Finally, the OK LED should turn green.

3. If the OK LED is green, the 8224 is working
correctly.

If the OK LED is not green, the 8224 is not working
correctly. See Appendix G, "Help and Service
Information" for instructions.

2-10 8224 Ethernet Stackable Hub

CHAPTER 3. 8224 ADMINISTRATION
_______________________________

Use Table 3-1 and Table 3-2 on page 3-3 to help you
determine which administrative actions are available for
your 8224 setup.

3-2 8224 Ethernet Stackable Hub

Chapter 3. 8224 Administration 3-3

Figure 3-1. Front View of the 8224 Models xx1 and xx2

ADMINISTRATIVE OPTIONS AVAILABLE FOR ANY 8224 SETUP
___________________________________________________

Whatever your 8224 setup, you can learn the status of an
8224 by viewing its LEDs or upgrade its microcode using
XMODEM. If you have more than one 8224 linked in a
stack, you can split the stack into two collision
domains. This section explains how.

If you have a Model xx2, either by itself or linked in a
stack, many more administrative actions are available to
you. See "Preparing for SNMP Management" on page 3-10
for details.

UNDERSTANDING THE LEDS

Table 3-3 on page 3-5 gives the meanings associated with
the 8224 status LEDs. The MEP LED functions only when a
MEP module is in the media expansion slot. The MEP LED
gives different messages depending upon which media
expansion port module is installed.

3-4 8224 Ethernet Stackable Hub

+-------------------------------------------------------+
| Table 3-3 (Page 1 of 2). 8224 Status LEDs |
+-------+---------------+-------------------------------+
| LED | APPEARANCE | MEANING |
| LABEL | | |
+-------+---------------+-------------------------------+
| OK | Off | No power. |
| +---------------+-------------------------------+
| | Green | The 8224 is working |
| | | correctly. |
| +---------------+-------------------------------+
| | Orange | Diagnostics are in progress. |
| +---------------+-------------------------------+
| | Blinking | The 8224 is not working |
| | Orange | correctly. |
+-------+---------------+-------------------------------+
| MGR | Off | The 8224 is not a manager |
| | | (Model xx1). |
| +---------------+-------------------------------+
| | Green | The 8224 is a manager (Model |
| | | xx2). |
+-------+---------------+-------------------------------+
| COL | Off | No collisions are detected. |
| +---------------+-------------------------------+
| | Blinking | Collisions are being |
| | Orange | detected. |
+-------+---------------+-------------------------------+
| MEP | Off | No activity. |
| (AUI) +---------------+-------------------------------+
| | Blinking | The AUI port is receiving |
| | Green | data. |
| +---------------+-------------------------------+
| | Orange | The AUI port is disabled. |
| +---------------+-------------------------------+
| | Blinking | The AUI port is partitioned. |
| | Orange | |
+-------+---------------+-------------------------------+
| MEP | Off | No activity. |
| (10BAS+---------------+-------------------------------+
| | Blinking | The 10BASE2 port is receiving |
| | Green | data. |
| +---------------+-------------------------------+
| | Orange | The 10BASE2 port is disabled. |
| +---------------+-------------------------------+
| | Blinking | The 10BASE2 port is |
| | Orange | partitioned. |
+-------+---------------+-------------------------------+

Chapter 3. 8224 Administration 3-5

Table 3-4 gives the meanings associated with the 10BASE-T
port status LEDs.

GETTING NEW MICROCODE

3-6 8224 Ethernet Stackable Hub

IBM PC Company Bulletin Board

The latest versions of 8224 microcode and the IBM 8224
Management Information Base (MIB) (file name IBM8224.MIB)
___________
are available on the IBM PC Company Bulletin Board System
(BBS).

To get the microcode:

1. Prepare your computer to call the IBM PC Company BBS.

You need a PC with a modem and communications
software in order to make the call. The BBS
auto-senses the speed of your modem, supporting
speeds between 1200 and 14 400 bps. Make sure that
your communications software is set to use 8 data
bits, no parity, 1 stop bit, and no flow control.

2. Dial one of the following numbers:

o United States (919) 517-0001
o Canada
- Vancouver (604) 664-6464
- Toronto (416) 946-4244
- Montreal (515) 938-3022
- Winnipeg (204) 934-2798
- Markham (905) 316-4255
- Hallifax (902) 420-0300

If you are a first-time user, you are prompted for
your first and last names, and then you are asked to
enter a password. You might want to write your
password in the following space.

+--- YOUR PASSWORD ---------------------------------+
| |
| IBM Personal Computer Company BBS password: |
| _________________ |
| |
+---------------------------------------------------+

3. At the main menu, enter REF DISK to sign the license
agreement.

Before you can download the file that contains the
microcode, you must complete the license agreement.

4. Find the file containing the microcode and download
it to your PC.

At the BBS's main menu, enter S and search for 8224.
____
The name of the microcode file has take the format
8224_ddd.exe, where ddd is a 3-digit number that
____________ ___
indicates its version. Return to the main menu, and

Chapter 3. 8224 Administration 3-7

then use your communications program to transfer the
microcode file to your PC. If your communications
software offers the option, receive the file in
binary form.
______

5. Decompress the microcode file.

At a DOS or OS/2 command prompt, enter 8224_DDD,
where ddd is the appropriate version number, and the
___
compressed file decompresses into three files:

o The microcode file, IBVd_dd.IMG
___________
o A sample text configuration file, 8224SAMP.CFG
____________
o A README file, README.TXT
__________

Internet

The latest 8224 microcode and MIB are also available on
the Internet. The files can be obtained through
ANONYMOUS FTP at either:

http://www.pc.ibm.com

http://lansupport.raleigh.ibm.com

UPGRADING MICROCODE USING XMODEM

This section explains how to send a microcode file to an
8224 using the XMODEM communications protocol. Sending a
microcode file to an 8224 using XMODEM presumes that:

o You have an ASCII text editor available
o There is an active serial link between your PC and
the Com port of the 8224
o You have on your PC a communications program that is
capable of transferring files in the XMODEM protocol

The following steps guide you through the process.

1. Use your text editor to create an upgrade request
file, formatted as shown in Figure 3-2 on page 3-9,
where d.dd is the appropriate version number of your
____
microcode file.

NOTE: Make certain that you type the microcode file
name correctly. When you send an upgrade request
file to the 8224, the microcode in the 8224 is
erased. You then have 3 minutes to begin sending the
microcode file to the 8224.

3-8 8224 Ethernet Stackable Hub

+----------------------------------------------------------------------------------+
| |
| |
| FV=IBVd.dd |
| ;end |
| |
| |

Figure 3-2. A Sample Microcode Upgrade Request File

2. Make a serial connection to the Com port of the 8224.

You can make the serial connection from your PC to
the 8224 in either of two ways:

o By directly attaching, using a null-modem cable,
or
o Over a modem connection

For more detail, see "Cabling Requirements for the
Com Port" on page 1-16.

If you make a null-modem connection, set your
communications software to 9600 bps. If you dial up
the 8224 over a modem connection, you can use speeds
of 9600, 2400, 1200, or 300 bps. Make sure that your
communications software is set to use 8 data bits, no
parity, 1 stop bit, and no flow control.

When you have established communications with the
8224, you should see strings of characters appearing
on your PC's screen in bursts. Wait for pauses
during which a C appears for an indication that the
8224 is ready to receive a file.

3. Use your communications software to send the upgrade
request file to the 8224. If your communications
software offers the option, send the file in binary
______
form.

o If the 8224 receives the file successfully, all
10BASE-T port status LEDs blink green twice, and
then the OK LED turns orange. The 8224 is not
able to be managed while the OK LED is orange,
but still functions as a repeater.

o If the 8224 does not receive the file
successfully (for example, if the ";end" line is
missing), the 10BASE-T port status LEDs blink
orange twice, and the OK LED stays green. The
microcode in the 8224 is not affected.

Chapter 3. 8224 Administration 3-9

4. Within 3 minutes, send the microcode file to the
________________
8224. If your communications software offers the
option, send the file in binary form.
______

o If the upgrade is successful, the OK LED changes
from orange to green, and the message "Flash Code
Valid -- Resetting to Flash" appears on your PC's
screen. The 8224 then starts a power-on
self-test (POST).

o If any failure occurs during the file transfer,
the OK LED stays orange. The 8224 is not able to
be managed, but still functions as a repeater.

SPLITTING A STACK

If the workstations attached to the stack are
experiencing performance delays due to network
congestion, one solution is to split the stack into two
or more collision domains. After the stack is split,
performance should improve.

Even if every 8224 in a stack is a Model xx1, you can
break the stack into two collision domains by removing
the hub expansion cable between any two 8224s. Remember
to remove the cable from the Out port first, to avoid
___
creating interference on the network.

You can re-enable communications between the stacks
without rejoining them into one collision domain by
interconnecting them using a bridge, router, or an
Ethernet switch. See "Interconnecting Segmented 8224s
Using Other Devices" on page 1-8 for details.

PREPARING FOR SNMP MANAGEMENT
_____________________________

In order to perform any of the management actions
discussed in this section, you must run an SNMP
management application, such as IBM StackWatch for
Windows or IBM StackWatch for NMS, on your workstation.
In addition, the stack you plan to manage must contain an
8224 Model xx2.

SNMP commands are sent over IP or IPX networks. If you
plan to use SNMP over an IP network, you first need to
set the IP addresses of the hubs in your stack; begin
with "Getting Started: SNMP over IP" on page 3-11. If
you plan to use SNMP over an IPX network, see "Disabling
BootP/RARP Requests" on page 3-16.

3-10 8224 Ethernet Stackable Hub

GETTING STARTED: SNMP OVER IP

To manage a stack using SNMP over IP, you must first set
the IP address of an 8224 Model xx2 using one of these
methods:

o By sending a configuration file using the XMODEM
protocol

o By configuring a BootP or RARP server to send the IP
address to the 8224 (see page 3-15)

o By using an IPX-based network management application
to discover the Model xx2, and then sending the IP
address over IPX (see page 3-16)

Assign IP addresses with care, especially if you plan to
communicate on the Internet. Duplicate addresses might
cause misrouting of frames and data loss.

Setting an IP Address Using XMODEM

Probably the simplest way to set the IP address is to
create a configuration file and then send it to an 8224
using the XMODEM communications protocol. The 8224
cannot be managed for the duration of the file transfer
but performs all repeater functions normally.

Sending a configuration file to an 8224 using XMODEM
requires all of the following:

o An ASCII text editor

o An active serial link between your PC and the Com
port of the 8224

o A PC communications program that is capable of
transferring files in XMODEM protocol

The following steps guide you through the process.

1. Use your text editor to create a configuration file,
formatted as shown in Figure 3-3 on page 3-12.

Chapter 3. 8224 Administration 3-11

Figure 3-3. A Sample Configuration File

Follow these rules when creating the configuration
file:

o Enter text in any combination of uppercase and
lowercase letters.
o End each line with a carriage return/line feed
(CR/LF).
o Keep line lengths under 132 bytes and the entire
file under 384 bytes.
o Do not use any spaces.
o Use only periods (.) as separators between IP
address octets.
o Start comment lines with a semicolon (;).
o End the file with a comment line.

Here are the meanings of each line of the
configuration file:

NOTE: Except for the FV line, you must enter a valid
______________________________________________
value for every line in the configuration file, even
____________________________________________________
if all the lines do not seem to apply to your setup.
____________________________________________________

FL Set FL to YES to change the rest of the
settings.

IP The 8224's IP address. Enter any valid IP
address, in dotted-decimal format, except
255.255.255.255.

NM The 8224's IP subnet mask. Enter any valid
subnet mask, except 0.0.0.0 or
255.255.255.255, in dotted-decimal format.

GW The IP default gateway, or default router,
address. Enter any valid IP address,
except 255.255.255.255, in dotted-decimal
format.

3-12 8224 Ethernet Stackable Hub

SI The IP address of the 8224's Com port (SI
stands for Serial IP address). If you do
not plan to use the Com port for SNMP
management, enter the value 0.0.0.0.

NOTE: Even if you do not plan to use the
Com port for SNMP management, you must
assign it a valid subnet mask (SM).

SM The IP subnet mask for the 8224's Com port.

Follow these rules when assigning a subnet
mask to the Com port:

o Choose a valid subnet mask for the Com
port.

o Choose a subnet mask for the Com port
that, when converted to a binary octet,
begins with 1.

Setting the first number of the subnet
mask at 128 or greater satisfies this
rule, for example: "128.0.0.0".

For details on conversion, see
"Converting Between Decimal and Binary
Values" on page C-1.

o Choose a subnet mask that, when
converted to a binary octet, has all
its 1s contiguous.

The subnet masks "128.0.0.0",
"192.0.0.0", and "224.0.0.0" follow
this rule; "193.0.0.0" does not.

For details on conversion, see
"Converting Between Decimal and Binary
Values" on page C-1.

o Make sure the 8224's IP address and the
Com port's IP address are on different
subnetworks.

That is, choose a subnet mask for the
Com port that, when logically ANDed to
the Com port's IP address, gives a
different result than the logical
ANDing of the repeater's IP address and
subnet mask.

See "Logically ANDing an IP Address and
a Subnet Mask" on page C-2 for an

Chapter 3. 8224 Administration 3-13

explanation of how to logically AND IP
addresses and subnet masks.

WC The write community name, or password, for
access to this 8224's management
information. You can use alphanumeric
characters and underscores. The maximum
length of the write community name is 20
characters.

FV The software version string (for example,
IBV1.30).

IMPORTANT: The presence of a valid FV line
will cause the existing Flash memory to be
erased and a new version downloaded. If
the FV line is not included, only the
configuration parameters will be updated.

2. Make a serial link to the Com port of the 8224.

You can make the serial link from your PC to the 8224
in either of two ways:

o By directly attaching, using a null-modem cable,
or
o Over a modem connection

For more detail, see "Cabling Requirements for the
Com Port" on page 1-16.

3. Use your communications software to send the
configuration file to the 8224. If your
communications software offers the option, send the
file in binary form.
______

o If the 8224 receives the file successfully, all
10BASE-T port status LEDs blink green twice.

o If the 8224 does not receive the file
successfully (for example, if "SM=" is not

3-14 8224 Ethernet Stackable Hub

followed by a valid subnet mask), the 10BASE-T
port status LEDs blink orange twice. Any
previous configuration information is not written
over.

Once one 8224 Model xx2 in a stack has an IP address, you
can set the IP addresses of all the other 8224s in that
stack by manipulating the ibm8224StackTable MIB object.
_________________
See "Inter-8224 Communications and the StackTable" on
page 3-17 for more information.

Setting an IP Address Using BootP or RARP

At the end of a POST, and every 5 minutes thereafter, the
8224 automatically sends out two Bootstrap Protocol
(BootP) requests, and then two Reverse Address Resolution
Protocol (RARP) requests.

NOTE: The number of retries and the interval between
requests is controlled by the ibm8224BootpRarpRetries and
_______________________
ibm8224BootpRarpInterval objects, respectively, in the
________________________
IBM 8224 MIB. The BootP and RARP requests contain the
MAC address of the 8224.

The requests seek a BootP or RARP server, which you must
have previously configured with an address resolution
__________________
table containing MAC addresses and corresponding IP
_____
addresses. When the BootP or RARP server receives the
request, it sends an IP address to the requesting 8224's
MAC address.

NOTE: BootP and RARP requests do not pass through
routers.

BootP and RARP servers vary from manufacturer to
manufacturer, so use the following example for reference
only. See your BootP or RARP server's documentation for
specific instructions.

Figure 3-4. A Sample BootP Configuration File

Chapter 3. 8224 Administration 3-15

In the preceding example, the first line is the locally
administered name of the device that is to receive the IP
address, "HT" is its hardware type, "HA" is its MAC
address, "IP" is its IP address, "SM" is its IP subnet
mask, and "GW" is its default gateway, or default router,
address.

Setting an IP Address Over IPX

If you plan to manage your stack using either IBM
StackWatch for Windows or IBM StackWatch for NMS, both
provide facilities for setting the IP addresses of 8224s
remotely.

Setting the IP address requires that:

o IPX networking software is installed on the
management workstation

o You know the MAC address and IPX network number for
the intended 8224, if it is on a different network
from your management workstation

Refer to the documentation included with your management
program for complete instructions.

DISABLING BOOTP/RARP REQUESTS: BootP requests disrupt
SNMP activity for 6 seconds every 5 minutes as long as an
8224 has no IP address, so you might want to disable them
if you do not plan to use the IP protocol. You disable
BootP and RARP requests by setting the IBM 8224 MIB
object ibm8224BootpRarpRequests to 2, noBootpRarp.
________________________ ___________

MANAGING 8224S USING SNMP
_________________________

Each of the management actions discussed in this section
requires an SNMP management application to issue
commands, such as IBM StackWatch for Windows or IBM
NetView for Windows, and an 8224 Model xx2 to enable the
Model xx1s in the stack to respond to commands.

References to MIB objects are made throughout the
discussions. If you have purchased a management
application developed specifically for the 8224, this
section might contain more detail than you require.

3-16 8224 Ethernet Stackable Hub

Refer to the documentation included with your management
application for specific instructions.

INTER-8224 COMMUNICATIONS AND THE STACKTABLE

The ibm8224StackTable MIB object, from the IBM 8224
_________________
private MIB, controls all 8224s in a managed stack,
regardless of whether they are segmented from the
external Ethernet bus. The information in this MIB
object is passed from 8224 to 8224 over the inter-hub
control bus in the hub expansion cables. See "Inter-8224
Communications in Managed Stacks" on page 1-5 for a
thorough explanation.

By using an SNMP management application to manipulate the
ibm8224StackTable MIB object, you can set IP information
_________________
for any 8224 in a managed stack and segment or rejoin any
8224 from or to the rest of the 8224s in the stack.

SEGMENTING AN 8224 FROM A STACK

Whether to segment an 8224 from a stack or to rejoin an
8224 to a stack is controlled by the ibm8224BkplNum MIB
______________
object, which is part of the ibm8224StackTable. Set
_________________
ibm8224BkplNum for the desired 8224 to 6 to segment an
______________
8224 from the external Ethernet hub expansion bus, or to
1 to rejoin the 8224 to the bus.

ENABLING OR DISABLING PORTS

Port enabling and disabling are controlled by the MIB
object rptrPortAdminStatus, which comes from RFC 1516.
___________________
Set rptrPortAdminStatus for the desired port to 2 to
___________________
disable the port, or to 1 to reenable the port.

ASSIGNING BACKUP PORTS

Assigning backup ports is controlled by the MIB object
ibm8224BkUpPortTable, which comes from the IBM 8224
____________________
private MIB.

The ibm8224BkUpPortTable object contains an entry for
____________________
each port in each 8224. To assign a backup port
(remember that you can set a port as a backup for another
only if they are both in the same 8224), set the object
ibm8224BkUpPortBackupPort to the number of the desired
_________________________
backup port.

To enable monitoring of the backed-up port, set the
object ibm8224BkUpPortBackupEnable to 2. To disable
___________________________

Chapter 3. 8224 Administration 3-17

monitoring, set ibm8224BkUpPortBackupEnable to 3. If
___________________________
ibm8224BkUpPortBackupEnable reads "4", the backup port
___________________________
has taken over for the primary port.

GETTING PERFORMANCE STATISTICS

To view the following performance statistics (and more),
get these MIB objects from the desired 8224:

o ibm8224GroupPortSummary
_______________________
o ibm8224PortCtrSummary
_____________________

These statistics are for the 8224 in general:

o Total frames
o Total octets
o Total partitioned ports
o Link status of all ports
o Backplane type (internal or isolated)
o Chassis ID (MAC address of the logical bottom hub)
o Slot number (1= topmost hub)

These statistics are for each port in an 8224:

o Readable frames
o Readable octets
o Auto-partition state
o Link test status
o Link state (whether up or down)
o Administrative status (whether enabled or disabled)
o Port type
o Operational status

All the counters are reset each time an 8224 is powered
down.

GETTING ERROR STATISTICS

To view the following error statistics (and more), get
these MIB objects from the desired 8224:

o ibm8224GroupPortSummary
_______________________
o ibm8224PortCtrSummary
_____________________

These statistics are for the 8224 in general:

o Total errors
o Transmit collisions
o Total partitioned ports
o Very long events

3-18 8224 Ethernet Stackable Hub

These statistics are for each port in an 8224:

o Total errors
o Collisions
o Auto-partitions
o Short events
o Runt frames
o Very long events
o Frames too long
o Late events
o Frame check sequence (FCS) errors
o Frame alignment errors
o Data rate mismatches
o Last source address
o Source address changes

All the counters are reset each time an 8224 is powered
down.

RECEIVING TRAPS

SNMP traps are messages sent by devices to network
_____
managers when certain changes occur at the device. Any
SNMP network manager can receive traps, as long as the IP
or IPX address of the manager's machine is entered into
either of these IBM 8224 private MIB objects at the
desired 8224: the ibm8224IPTrapReceiverTable or the
__________________________
ibm8224IPXTrapReceiverTable. Each trap receiver table
___________________________
can hold up to 10 managers' addresses.

SNMP management applications developed specifically for
the 8224 simplify the setting of trap receiver addresses;
see their documentation for details.

The following traps are sent by the 8224:

HEALTH STATE TRAP: Notifies the network manager that
there has been a change in the health state of the 8224.
One of three possible messages are sent:

o Port auto-partitioned
o Backup port activated
o Intrusion detected and the port disabled

GROUP MAP CHANGE TRAP: Notifies the network manager that
there has been a change in the layout of the stack due to
an interruption in the inter-hub command bus. This
message is sent when an 8224 is hot-swapped or fails.

AUTHENTICATION FAILURE TRAP: Notifies the network
manager that an 8224 received an SNMP request that was
not correctly authenticated: that is, the request did not
contain a valid Write Community name.

Chapter 3. 8224 Administration 3-19

COLD START TRAP: Sent by Model xx2 only, after a
power-on reset.

SNMP MANAGEMENT THROUGH THE COM PORT
____________________________________

By making a serial link to a Com port of any 8224 in a
managed stack, you have an alternative means of managing
a stack of 8224s using SNMP.

To take advantage of this function, you must use the
Serial Line Internet Protocol (SLIP). SLIP is provided
with most TCP/IP software; check the documentation
included with your TCP/IP software.

Before you can use the Com port for SNMP, you must assign
the Com port an IP address and a subnet mask of its own.
This means that any 8224 you manage using SNMP through
the Com port has two IP addresses and two subnet masks.
One pair is for the repeater, and the other pair is for
the Com port.

Only one SLIP session between a manager and a stack can
be active at one time.

ASSIGNING AN IP ADDRESS AND SUBNET MASK TO THE COM PORT

The only way to set IP information for the Com port is by
making a serial connection from your management station
to the Com port, and then sending a configuration file to
the 8224 using XMODEM (see "Setting an IP Address Using
XMODEM" on page 3-11 for instructions). The "SI=" and
"SM=" lines set the Com port's IP address and subnet
mask, respectively.

STARTING A SLIP SESSION

1. Make a serial link to the Com port of the 8224.

You can make the serial link from your PC to the 8224
in either of two ways:

o By directly attaching, using a null-modem cable,
or
o Over a modem connection

For more detail, see "Cabling Requirements for the
Com Port" on page 1-16.

If you make a null-modem connection, set your
communications software to 9600 bps. If you dial up
the 8224 over a modem connection, you can use speeds

3-20 8224 Ethernet Stackable Hub

of 9600, 2400, 1200, or 300 bps. Make sure that your
communications software is set to use 8 data bits, no
parity, 1 stop bit, and no flow control.

2. Using your TCP/IP software, start a SLIP session
between the IP address of your management
workstation's Com port and the IP address of the
8224's Com port.

3. Using your TCP/IP software, set up a route to the
repeater's IP address through the 8224's Com port's
_______
IP address. This enables SNMP commands to reach the
repeater.

Until you assign a default gateway to each 8224 in the
stack, you are unable to manage them. Continue with
"Assigning Default Gateways to the Stack."

ASSIGNING DEFAULT GATEWAYS TO THE STACK

You have two options for assigning a default gateway to
the stack:

o You can set the 8224 with which you have set up the
SLIP session (called the SLIP 8224 for this
_________
discussion) as the default gateway or,

o You can set a router outside the stack as the default
gateway.

There are advantages and disadvantages to each option.

If you set the SLIP 8224 as the default gateway, SNMP
commands from your workstation travel the shortest path
to whichever 8224 you want to manage. If the IP address
of the SLIP 8224 changes (or if you SLIP to a different
8224), however, you need to set the new default gateway
address to each of the 8224s in the stack.

If you set an external router as the default gateway, and
the IP address of the SLIP 8224 changes, you need to set
the new default gateway address only once, at the
external router. The disadvantage is that SNMP commands
from your workstation to the 8224 you want to manage must
travel a longer path.

Chapter 3. 8224 Administration 3-21

If the SLIP 8224 Will Be the Default Gateway

1. Using a MIB browser, get the ibm8224StackTable MIB
_________________
object from the SLIP 8224.

2. Set the default gateway for the SLIP 8224 to
"0.0.0.0".

The SLIP 8224 acts as an IP router, directing SNMP
commands to the other 8224s in the stack, provided
that there is an Ethernet link between the management
workstation and the 8224 you want to manage. (For
more detail, see "Linking Segmented 8224s" on
page 1-7.)

NOTE: Without an Ethernet link from the management
workstation to the 8224 you want to manage, you can
still set IP information for an 8224 and rejoin it to
the stack. The inter-hub control bus makes these
actions possible.

3. Set the default gateway for each of the other 8224s
in the StackTable to the SLIP 8224's repeater's IP
address.

Each of the other 8224s in the stack send SNMP
information to the SLIP 8224, which routes the
information to the SNMP manager attached to its Com
port.

Once you have set default gateways for all the 8224s in
the stack, you can manage them just as if your management
station were attached to any Ethernet port in the 8224.

If an External Router Will Be the Default Gateway

1. Using a MIB browser, get the ibm8224StackTable MIB
_________________
object from the SLIP 8224.

2. Set the default gateway for each 8224 in the stack to
the IP address of the external router.

When the SLIP 8224 receives SNMP commands from your
management workstation, it directs the commands to
the external router, which then directs the commands
to the 8224 you want to manage. The commands reach
the 8224 you want to manage as long as there is an
Ethernet link between the management workstation and
the 8224 you want to manage. (For more detail, see
"Linking Segmented 8224s" on page 1-7.)

NOTE: Without an Ethernet link from the management
workstation to the 8224 you want to manage, you can

3-22 8224 Ethernet Stackable Hub

still set IP information for an 8224 and rejoin it to
the stack. The inter-hub control bus makes these
actions possible.

Once you have set default gateways for all the 8224s in
the stack, you can manage them just as if your management
station were attached to any Ethernet port in the 8224.

UPGRADING MICROCODE USING TFTP
______________________________

Microcode upgrades done using TFTP require the support of
a TCP/IP network. If your network does not use TCP/IP
for internetwork communications, use the method described
in "Upgrading Microcode Using XMODEM" on page 3-8.

The first two methods described here, "MIB-Triggered
Upgrade through Any Ethernet Port" and "MIB-Triggered
Upgrade through the Com Port," require setting MIB
variables to start the upgrade; the third,
"BootP-Triggered Upgrade" on page 3-26, does not, but
requires a BootP/TFTP server.

MIB-TRIGGERED UPGRADE THROUGH ANY ETHERNET PORT

The objects that control microcode upgrades are in the
IBM 8224 private MIB.

The information here is given primarily for the benefit
of those who use a MIB browser to perform an upgrade. If
you have purchased IBM StackWatch for Windows or the 8224
Application for IBM NetView for Windows, you have a
simpler way to perform upgrades; see their documentation
for instructions.

1. Get the microcode file (for instructions, see
"Getting New Microcode" on page 3-6) and copy it to a
directory in your TFTP server, for example:

c:\ibm\microcod

2. Using a MIB browser, get the following MIB objects
from the 8224 to which you want to send the microcode
upgrade, then set them as you require:

IBM8224DOWNLOADIMAGEPATHNAME: The fully qualified path
name, in the TFTP server, where the microcode file can be
found, for example:

c:\ibm\microcod

Chapter 3. 8224 Administration 3-23

IBM8224DOWNLOADSERVERIP: The IP address of the TFTP
server, in dotted-decimal format, for example:

9.67.12.123

IBM8224DOWNLOADIMAGEVERSION: The version number of the
microcode file to send, in the format IBVd.dd, for
example:

IBV1.01

IBM8224DOWNLOADSTATE: Set to 2 to start sending the
file.

NOTE: The microcode in the 8224 is erased when the 8224
receives the setting for ibm8224DownloadState. If any
____________________
error occurs in the microcode file transfer, the only way
the 8224 accepts new microcode is by using XMODEM. See
"Upgrading Microcode Using XMODEM" on page 3-8 for
instructions.

MIB-TRIGGERED UPGRADE THROUGH THE COM PORT

Through a SLIP connection to the Com port of an 8224, you
can upgrade the microcode in any 8224 in the same stack.

Upgrading microcode through the Com port assumes that you
have configured your 8224 in accord with the guidelines
in "SNMP Management through the Com Port" on page 3-20.

If you are running the 8224 Application for IBM NetView
for Windows on your workstation, the capability to
perform SLIP/TFTP downloads is built into the
application. See its documentation for instructions.

If you are not running the 8224 Application for IBM
___
NetView for Windows on your workstation, you need the
following software installed on your workstation before
you can upgrade microcode using SLIP/TFTP:

o A TCP/IP stack

o Communications software capable both of making a SLIP
connection and of transferring files using TFTP

o An SNMP manager with a MIB browser

To upgrade the microcode:

1. Get the microcode file (for instructions, see
"Getting New Microcode" on page 3-6) and copy it to a
directory in your workstation, for example:

3-24 8224 Ethernet Stackable Hub

c:\ibm\microcod

2. Make a serial connection to the Com port of the 8224.

You can make the serial connection from your PC to
the 8224 in either of two ways:

o By directly attaching, using a null-modem cable.
o Over a modem connection. See "Cabling
Requirements for the Com Port" on page 1-16.

3. Using your communications software, start a SLIP
session with the 8224.

4. Using your MIB browser, get the following MIB objects
from the 8224 to which you want to send the microcode
upgrade, and then set them as you require:

IBM8224DOWNLOADIMAGEPATHNAME: The fully qualified path
name, in your workstation, where the microcode file can
be found, for example:

c:\ibm\microcod

IBM8224DOWNLOADSERVERIP: The IP address of your
workstation, in dotted-decimal format, for example:

9.67.12.123

IBM8224DOWNLOADIMAGEVERSION: The version number of the
microcode file to download, in the format IBVd.dd, for
example:

IBV1.01

IBM8224DOWNLOADSTATE: Set to 2 to start sending the
file.

Chapter 3. 8224 Administration 3-25

BOOTP-TRIGGERED UPGRADE

Each 8224 automatically makes two BootP requests at the
end of the POST and every 5 minutes thereafter. The
BootP requests contain the MAC address of the 8224.

The requests seek a BootP/TFTP server, on which you must
have previously loaded a new microcode file (follow the
steps in "Getting New Microcode" on page 3-6 to get a
microcode file). When the BootP server receives a
request, it locates the microcode file and sends it to
the 8224's IP address using TFTP.

NOTES:

1. The BootP and TFTP servers must have the same IP
address

2. BootP requests do not pass through routers

BootP servers vary from manufacturer to manufacturer, so
use the following example for reference only. See your
BootP or RARP server's documentation for specific
instructions.

Figure 3-5. A Sample BootP/TFTP Download File

In Figure 3-5, the first line is the locally administered
name of the device that receives the download, "HT" is
the hardware type, "HA" is the MAC address, "IP" is the
8224's IP address, "SM" is the 8224's IP subnet mask,
"GW" is the 8224's default gateway, or default router,
address, "BF" is the boot file name (the microcode file
name), and "HN:" is required for a successful TFTP
download.

3-26 8224 Ethernet Stackable Hub

MANAGING THE 8224 USING THE VT100 INTERFACE
___________________________________________

As an alternative to management using SNMP, the 8224 can
also be managed through a VT100 terminal interface. All
of the available management functions are described in
"VT100 Panels" on page 3-28.

COMMUNICATION ALTERNATIVES

There are three ways to communicate with the 8224 VT100
interface. Over the:

o Com Port using VT100 protocol over a modem or direct
connection using a null-modem cable.
o Ethernet using Telnet/IP
o Com Port using Telnet/SLIP

Only one VT100 session is allowed on a single VT100
interface. If, for example, you establish a VT100
session over the Ethernet, you cannot establish another
session over the Com Port.

Ethernet

A VT100 session is established over the IP Ethernet
connection using Telnet with IP. Starting a Telnet
session with an 8224 automatically invokes a VT100
session.

Com Port

A VT100 is invoked through the Com Port using either
Telnet with SLIP, or direct VT100 protocol. When using
Telnet, the VT100 session is invoked automatically when
the Telnet session is started.

When using VT100 protocol, the VT100 session is invoked
by the key sequence 'VT100'. See "VT100 Protocol
Management Through the Com Port" for more information.

VT100 PROTOCOL MANAGEMENT THROUGH THE COM PORT: When the
8224 is powered on, after the software enters the Runtime
mode, it issues a modem initialization string to the Com
port once every 10 seconds. Each string is issued at a
different data rate (9 600, 2 400, 1 200, and 300 bps) in
an effort to match the data rate at the interface. If a
terminal running VT100 communications software is
connected to the Com port either through a modem or a
null-mode cable running at one of the above data rates, a
match will occur and a readable alphanumeric character
string (for example, "at&fs0=1") appears on the terminal

Chapter 3. 8224 Administration 3-27

screen. To start the VT100 session follow this
procedure:

1. Within 20 seconds after the appearance of the
readable character string, enter VT100. The Login
panel appears (see "Login" on page 3-31).

NOTE: If, after the readable character string
appears, you do not enter vt100 before 20 seconds
elapses, you must wait for the 8224 to recycle and
issue a new initialization string.

2. Within 20 seconds after the Login screen appears,
enter the password. (The default password is
"public") The Main panel appears (see "Main" on
page 3-32).

NOTE: If, after the Login panel appears, you do not
enter a valid password before 20 seconds elapses, the
session is automatically terminated and you must
return to the beginning of the process.

VT100 PANELS

Once the VT100 session is established, the 8224
management functions are controlled through a series of
menu and data panels that appear on your workstation
screen. The following keys are active and have the
function described:

ENTER The Enter key validates an entry in a
field. If the entry is not valid, an
error message appears in the panel
and the highlight bar remains on the
field. If the data is valid, the
data is accepted, and no error
message appears. If the field is an
exit option, processing proceeds to
the next panel. Only the Enter key
can be used to exit a panel. If the
field is not an exit option, the
highlight bar moves to the next
field.

TAB The Tab key moves the highlight bar
from field to field in the forward
direction. If the field has changed,
the data is validated. If the entry
is not valid, an error message
appears in the panel. If the data is
valid, it is accepted, no error
message appears, and the highlight

3-28 8224 Ethernet Stackable Hub

bar moves to the next field. The Tab
key cannot be used to exit a panel.

CURSOR (ARROW) KEYS The cursor keys move the highlight
bar from field to field. The right
or down arrow moves the bar forward;
the left or up arrow moves the bar
backward. If the field has changed,
the data is validated. If the entry
is not valid, the original content of
the field is restored. If the entry
is valid, the new data remains in the
field but is not accepted. The data
is accepted only when you exit the
field using the Tab or Enter key.

SPACE BAR The space bar is used to scroll the
contents of an Update field (see
"Update" on 3-29) through a range of
predefined settings. In an Edit
field (see "Edit" on 3-30), the space
bar generates a space character.

BACKSPACE The Backspace key is used to correct
errors in an Edit field. Pressing
the Backspace key deletes the
character in the cursor position.

NOTE: If you are using the Windows Terminal Program, the
Use Function, Arrow, and Control Keys for Windows check
box must not be selected. To verify this, select
Settings from the menu bar, then select Terminal
Preferences. The indicated check box is at the bottom of
the Terminal Preferences dialog box.

The VT100 panels contain three types of fields:

SELECTION These fields cannot be edited nor can
their setting be changed. They are
selected by placing the highlight bar
on the field and pressing the Enter
key. Selection field text is not
highlighted.

UPDATE These fields cannot be edited. They
are delimited on the screen by the <
and > characters. Their contents are
changed by scrolling through a set of
predefined settings using the space
bar. All changes to an Update field
are immediately accepted when they
are made.

Chapter 3. 8224 Administration 3-29

EDIT The contents of an Edit field can be
edited. Edit fields are identified
on the screen by highlighted text.

The contents of an Edit field are
changed using the alphanumeric keys.
Use of the cursor keys in an Edit
field moves the highlight bar to the
next field The Tab or Enter key must
be used to accept any changes made to
an Edit field. The Backspace key is
used to correct errors.

With the exception of the Login panel, all panels provide
the following information:

o System name in the upper-left corner
o IP address in the upper-right corner
o System time in the lower-right corner

The following sections describe each panel and the
functions they control in detail.

3-30 8224 Ethernet Stackable Hub

+----------------------------------------------------------------------------------+
| |
| Login |
| Enter the password and press Enter |
| (error messages are displayed here) |
| |
| |
| |
| |
| |
| |
| Password: ****** |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------------------------------------+

Possible error messages:

ERROR: Password incorrect, please reenter

A valid password must be entered on this screen in order
to progress to the next screen. The password consists of
up to six characters, which are obscured on the screen by
an asterisk (*) when typed. The backspace key is used to
correct errors. After typing all the password
characters, press ENTER. If the password entered is
incorrect, an error message appears on line 3. There is
no limit on the number of attempts to enter a password.

The appearance of this panel is considered the start of a
session. If a valid password has not been entered within
a specific time (currently 20 seconds) of the start of
the session, it is automatically terminated.

Chapter 3. 8224 Administration 3-31

Main

Main follows successful entry of a valid password on the
Login panel. It provides a selection menu of available
management functions.

You select one of the available management functions in
either of two ways:

1. Use the cursor keys to highlight the desired
function, and then press ENTER

2. Highlight the Selection data field and enter the
letter of the desired function. This data field is
not case-sensitive.

Except for Logout, you can return to Main from any of the
management function panels.

3-32 8224 Ethernet Stackable Hub

System Information

System Information provides fields for the entry of
system data and the control of system functions.

Possible error messages:

ERROR: Value is too small

ERROR: Value is too large

ERROR: Value must be in the range Õ0..255þ

After all desired changes have been made to the edit and
update fields you can do either of two things:

1. Accept the changes by placing the cursor in the
Accept edit field and pressing Enter. You return to
Main.

2. Cancel the changes by placing the cursor in the
Cancel edit field and pressing Enter. You return to
Main.

Errors are displayed on line 3.

Chapter 3. 8224 Administration 3-33

Port Statistics

Port Statistics displays port information. It is also
used to enable and disable ports.

Port information is displayed for four ports at a time.
Information for additional ports is obtained by using the
cursor keys to scroll the information left and right.
The number of ports scrolled with each depression of the
cursor key is set by entering a number from 1 to 9 in the
Scroll edit field.

Port Link has three possible states:

1. Partition

The port is partitioned out of the network.

2. Up

The link is present

3. Down

The link is not present

3-34 8224 Ethernet Stackable Hub

Port State is an update field that can be toggled between
Enabled and Disabled.

To return to Main, place the cursor in the Return to menu
edit field and press ENTER.

Chapter 3. 8224 Administration 3-35

Backup Port Configuration

Backup Port Configuration displays information on backup
ports. It also allows backup ports to be configured.

+----------------------------------------------------------------------------------+
| |
| IBM Corp. Backup Port Configuration IP: 143.162.208.010 |
| |
| Use '+' and '-' keys to select and entry. |
| (error messages are displayed here) |
| Primary Backup |
| Entry Port Port State |
| -------------------------------------------------- |
| 1 2 1 Tripped |
| 2 4 3 Enabled |
| 3 6 5 Disabled |
| - - - - |
| - - - - |
| - - - - |
| - - - - |
| - - - - |
| - - - - |
| -------------------------------------------------- Action |
| -- -- <-------> <------> |
| |
| |
| |
| |
| |
| Return to menu _ 0 hours, 19 minutes |
| |
+----------------------------------------------------------------------------------+

Possible error messages:

ERROR: Unable to set backup port

ERROR: Unable to set backup status

ERROR: Unable to delete

ERROR: Unable to update status

This panel displays the contents of the Backup Port
Table. Up to nine entries at a time can be displayed.
The + and - keys are used to move the selection up and
down in the list. If there are more than nine entries in
the table, the contents of the list will scroll as the
selection moves to the bottom or top of the panel. The
Primary Port column identifies the ports that have a
backup port assigned. The Backup Port column identifies
the backup port assigned to the port in the Primary Port

3-36 8224 Ethernet Stackable Hub

column. The State column identifies the status of the
backup port:

o Enabled

Monitoring of the primary port is enabled. The
backup port is partitioned and will take over for the
primary port if the primary port fails.

o Disabled

Monitoring of the primary port is disabled. The
backup port will not take over if the primary port
fails.

o Tripped

The backup port has taken over for the primary port.

Below the box containing the list, are four fields. The
fields under the Primary Port, Backup Port, and State
columns are filled in with appropriate information as you
scroll through the list with the + and - keys. When an
existing entry appears in these fields, you can update or
delete it. When a blank entry appears, you can add a new
entry to the table.

The Action field is a an update field that has three
possible settings:

1. Update

Changes the settings for the selected entry to the
setting specified in the Primary Port, Backup Port,
and State fields.

2. Delete

Removes the selected entry from the table.

3. Add

Adds a new entry to the table with the setting
specified in the Primary Port, Backup Port, and State
fields.

The State field is an update field that has the three
possible settings as described above for the State
column.

To add a new entry, select an empty slot in the table.
Specify the desired settings in the Primary Port, Backup
Port, and State fields. Then, select ADD in the Action
field.

Chapter 3. 8224 Administration 3-37

All changes or additions are validated when you press the
Enter, Tab, or down cursor key. If errors are detected
they are displayed in line 4. You can configure multiple
entries without leaving the panel. When you have
finished configuring backup ports, place the cursor in
the Return to menu edit field and press ENTER. You will
return to Main.

3-38 8224 Ethernet Stackable Hub

Stack Configuration

Stack Configuration is used to configure other hubs in
the stack.

+----------------------------------------------------------------------------------+
| |
| IBM Corp. Stack Configuration IP: 143.162.208.010 |
| |
| Use '+' and '-' keys to scroll to the next unit. |
| |
| Backplane Type <non-isolated> |
| IP Address XXX.XXX.XXX.XXX |
| IP Netmask XXX.XXX.XXX.XXX |
| Default Gateway XXX.XXX.XXX.XXX |
| |
| |
| |
| |
| |
| Unit 1 |
| |
| Cancel changes _ Accept changes _ |
| |
| |
| |
| |
| |
| |
| |
| Return to menu _ 0 hours, 1 minutes |
| |
+----------------------------------------------------------------------------------+

Use the + and - keys to select which hub you want to
configure. The selected hub is displayed in the Unit
field. Specify the Backplane type by selecting a setting
from the Backplane Type update field. The IP Address ,
IP Netmask, and Default Gateway address are entered in
those edit fields respectively.

After all changes have been made, you can choose to:

1. Accept the changes by placing the cursor in the
Accept changes edit field and pressing Enter. You
return to Main.

2. Cancel the changes by placing the cursor in the
Cancel changes edit field and pressing Enter. The
fields are restored to their previous settings and
you remain in Stack Configuration.

Chapter 3. 8224 Administration 3-39

3. Cancel the changes by placing the cursor in the
Return to menu edit field and pressing Enter. You
return to Main.

3-40 8224 Ethernet Stackable Hub

Change Password

Change Password is used to change the password required
to log into the VT100 session.

+----------------------------------------------------------------------------------+
| |
| IBM Corp. Change Password IP: 143.162.208.012 |
| |
| Enter the new password in both New and Verify password and press Enter. |
| (error messages are displayed here) |
| |
| |
| |
| |
| |
| |
| |
| Old password: |
| |
| New password: |
| |
| Verify password: |
| |
| |
| |
| |
| |
| |
| |
| |
| Cancel changes _ 0 hours, 1 minutes |
| |
+----------------------------------------------------------------------------------+

Possible error messages:

ERROR: Old password not valid

ERROR: Verify password does not match New password

To change a password the old (current) password must be
entered along with the new password (twice). The second
entry of the new password is used to verify the first
entry. The new password is not accepted if the New
password and Verify password do not match.

The password can be up to six characters in length. All
of the password characters, old and new, are obscured by
asterisks (*) as you enter them. The Backspace key is
used to correct errors. The default password is
"public".

Chapter 3. 8224 Administration 3-41

The VT100 session password is stored in the MAC Address
PROM along with the other 8224 security settings.

After the Old, New, and Verify passwords are entered you
can either:

1. Process and accept the changes by pressing Enter.
You return to Main.

2. Cancel the changes by placing the cursor in the
Cancel changes edit field and pressing Enter. You
return to the Main screen.

3-42 8224 Ethernet Stackable Hub

Download Firmware

Download Firmware allows you to request a download of new
Runtime microcode.

+----------------------------------------------------------------------------------+
| |
| IBM Corp. Download Firmware IP: 143.162.208.010 |
| |
| Toggle selections to download firmware using XMODEM protocol or TFTP |
| (error messages are displayed here) |
| |
| |
| |
| Protocol type < XMODEM > |
| |
| Version IBV1.30 |
| |
| TFTP Firmware Download Parameters |
| (required only for a TFTP download) |
| |
| TFTP server IP address 000.000.000.000 |
| |
| Filename |
| |
| |
| |
| |
| |
| |
| Return to menu _ Start download _ 0 hours, 19 minutes |
| |
+----------------------------------------------------------------------------------+

Possible error messages:

ERROR: The field must be in the range Õ0..255þ

ERROR: Invalid parameter set

ERROR: Version string invalid

ERROR: Invalid product identifier

ERROR: Invalid version identifier

ERROR: Invalid unit type

ERROR: Invalid major version number

Downloads are accomplished using either XMODEM or SLIP
protocol. Which protocol is used is determined by the
type of VT100 session in use. The three possible types
of VT100 sessions are:

Chapter 3. 8224 Administration 3-43

o Telnet/IP over the Ethernet
o Telnet/SLIP over the Com Port
o Direct VT100 protocol over the Com Port

XMODEM protocol is used with the direct VT100 protocol
session, and TFTP is used with either of the Telnet
sessions.

Select the download protocol, XMODEM or TFTP, in the
Protocol type update field. The version of the Runtime
code to be downloaded is specified in the Version edit
field. The version string is the same as used for BootP
configuration of the Host Name. If you select TFTP, the
TFTP server IP address and the file name of the Runtime
code must also be specified.

After you have entered all of the required information,
you can choose to:

1. Start the download by placing the cursor in the Start
download edit field and pressing Enter. After the
download is complete, you return to Main.

2. Cancel the download by placing the cursor in the
Return to menu edit field and pressing Enter. You
return to Main.

3-44 8224 Ethernet Stackable Hub

Modem Setup

Modem Setup allows the user to define a modem
initialization string and to control automatic
negotiation.

+----------------------------------------------------------------------------------+
| |
| IBM Corp. Modem Setup IP: 143.162.208.012 |
| |
| Enter the command string for initializing the modem. |
| |
| |
| |
| |
| |
| |
| |
| Initialization String: AT&FX1E0Q0V1&C1S0=1S12=5 |
| |
| Auto Negotiation: <Enabled > |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| Cancel changes _ Accept changes _ 0 hours, 19 minutes |
| |
+----------------------------------------------------------------------------------+

The default modem initialization string is shown in this
panel. These modem settings established by this string
are:

o Factory settings
o Smartmodem 1200 mode
o Echo off
o Modem response on*
o Verbose on*
o DCD asserted*
o Auto-answer on 1 ring*
o Escape sequence guard time = 100 ms

You can enter a different command sequence of up to 40
characters in the Initialization String edit field. In
order for the MDC100 firmware to work correctly, the
settings marked with an * in the above list should not be
changed. It is also recommended that Echo be set to off.

Chapter 3. 8224 Administration 3-45

You can set the Auto Negotiation update field to Enabled
or Disabled. If your modem supports automatic
negotiation, it is recommended that this setting be
enabled.

After you have made all desired changes to the edit and
update fields, you can do either of two things:

1. Accept the changes by placing the cursor in the
Accept edit field and pressing Enter. You return to
Main.

2. Cancel the changes by placing the cursor in the
Cancel edit field and pressing Enter. You return to
Main.

3-46 8224 Ethernet Stackable Hub

Logout

Logout allows you to log out of the current VT100
session.

+----------------------------------------------------------------------------------+
| |
| IBM Corp. Logout IP: 143.162.208.012 |
| |
| To end the session, toggle the selection to yes and press Enter. |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| End session <Yes> |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| 0 hours, 32 minutes |
| |
+----------------------------------------------------------------------------------+

The End session update field provides two choices:

1. Pressing Enter with Yes displayed in the update field
logs you out of the current session and returns to
Login.

2. Pressing Enter with No displayed in the update field
leaves you in the current session and returns to
Main.

Chapter 3. 8224 Administration 3-47

PORT INTRUSION PROTECTION
_________________________

The port intrusion protection feature provided by the
8224 is used to prevent unauthorized stations from
accessing the network.

IMPORTANT: This protection is implemented at the port
level and is based on the MAC address. Only one
authorized MAC address can be specified per port.
Therefore, this protection feature is used only on a port
that has a single source or device sending and receiving
frames.

Do not enable port intrusion protection for an uplink
port that receives multiple MAC addresses. If you do,
the 8224 will partition the port when it receives an
unauthorized MAC address.

ACTIVATING INTRUSION PROTECTION

Port intrusion protection is activated by using SNMP to
set two MIB objects:

1. ibm8224IntrusionPortStatus
__________________________
2. ibm8224IntrusionMACAddress or
__________________________
ibm8224IntrusionMACAddressStr
_____________________________

Protection is enabled or disabled using the
ibm8224IntrusionPortStatus object. This object can have
__________________________
one of three settings:

1. 1 - Protection is enabled
2. 2 - Protection is disabled
3. 3 - Intrusion has been detected (tripped - see
"Intrusion Detection" on page 3-49)

Set the object to 1 to enable protection or to 2 to
disable protection.

NOTE: Any attempt to change the status of the
ibm8224IntrusionPortStatus object using management
__________________________
software when it is set to enabled(1), results in a
Protocol Data Unit (PDU) error. See "Security" on
page 3-49 for more information.

The authorized MAC address is supplied in the
ibm8224IntrusionMACAddress or
__________________________
ibm8224IntrusionMACAddressStr object. Because the
_____________________________
intrusion protection feature is secured against
unauthorized alterations to the protection settings, the
authorized MAC address should be set before protection is
enabled.

3-48 8224 Ethernet Stackable Hub

INTRUSION DETECTION

When an intrusion is detected, the port on which the
intrusion was detected is partitioned, the
ibm8224IntrusionPortStatus object is set to 3 (tripped),
__________________________
and a Health State trap is generated (see "Receiving
Traps" on page 3-19) indicating the number of the
disabled port. An intruder is detected when frames
received from the intruder do not have a MAC address that
matches the authorized MAC address. Obviously, an
intruder that never sends a frame is not detected.

After a port is partitioned due to an intrusion, it
remains so until management software reenables the port
(set the rptrBasPortAdminState object in the Novell MIB
_____________________
to 2 (enable)), or disables intrusion protection. This
is the case even through hub power interruptions or
management-initiated resets.

SECURITY

Port intrusion security prevents unauthorized alterations
to the intrusion protection settings. This includes both
the status and authorized address objects. Any changes
to the intrusion protection settings must be made with an
SNMP manager that supports security. You cannot change
intrusion protection settings using an MIB browser.

AUTO-DISCOVERY
______________

The 8224 supports both IP and IPX automatic discovery
mechanisms. Automatic discovery is the ability of a
network manager to discover the node address and
functional capability of network devices.

IP AUTO-DISCOVERY

IP auto-discovery is used by most SNMP platforms (for
example, NetView 6000). In order to be discovered, a
network device must transmit an Internet Control Message
Protocol (ICMP) PING . Transmission of this PING is
controlled in the 8224 by the MIB object
ibm8224IPAutoDiscoveryState. Transmission can be enabled
___________________________
or disabled. The default state of this object is
enabled.

The information obtained by auto-discovery is kept in the
Address Resolution Protocol (ARP) cache of the gateways
and routers of the network. The gateways and routers
employ a cache-aging process that removes addresses that
have not be detected within a specified time. If IP

Chapter 3. 8224 Administration 3-49

auto-discovery is enabled, the 8224 periodically
transmits the ICMP PING to keep its address in the
gateway cache. The rate that the PING is transmitted is
controlled by the ibm8224PingPacketRate MIB object. This
_____________________
rate should be set to a value less than the cache-aging
timer. The aging timer in the gateway is typically 60
seconds. The 8224 default PING rate is once every 55
seconds.

Both IP auto-discovery MIB objects are stored in
nonvolatile memory.

NOVELL IPX AUTO-DISCOVERY

IPX auto-discovery requires that the 8224 transmit a
Services Advertising Protocol (SAP) message.
Transmission of the SAP message is controlled by the
ibm8224IPXSapBroadcast MIB object, which is store in
______________________
nonvolatile memory. Transmission can be enabled or
disabled. The default state of this object is enabled.

In the same manner as IP auto-discovery, the Novell
servers keep a cache of available services that is
subject to the aging process and is updated every 60
seconds. When IPX auto-discovery is enabled, the 8224
transmits the SAP message every 55 seconds. There is no
MIB object that controls the SAP message rate.

RJ-45 AUTO-POLARITY REVERSAL
____________________________

Automatic polarity reversal is a port-level feature that,
when enabled, automatically corrects the polarity of the
RJ-45 port in the event of a wiring error. This feature
does not apply to the MEP or HEP ports. The feature can
be enabled or disabled by setting the
ibm8224AutoPolarityReversal object in the IBM 8224 MIB.
___________________________
When a hub is initialized, the feature is automatically
enabled. It will be disabled if the hub is reset.

3-50 8224 Ethernet Stackable Hub

CHAPTER 4. SERVICING 8224S
___________________________

8224s contains no serviceable parts. Each 8224 is a
field-replaceable unit (FRU). See "Hot-Swapping 8224s"
for 8224 replacement instructions.

If you need to order replacement parts for an 8224, see
"Parts" on page 4-3.

HOT-SWAPPING 8224S
__________________

You can unplug the hub expansion cable from an 8224 and
plug it into a replacement 8224 without switching off the
power to the other 8224s in the stack (that is, you can
hot-swap 8224s).

If you hot-swap an 8224, the hub expansion ports will
take 1 or 2 minutes to resynchronize. While the stack
resynchronizes, it will appear split to a network manager
and management commands might not reach a desired 8224.
Remember that this is a temporary condition, and that
each 8224 performs repeater functions normally while
resynchronizing.

To hot-swap an 8224:

1. Switch OFF the power to the 8224 you will swap; then,
disconnect power from the back of the unit:

o Models 001 and 002 -- unplug the ac power cord.
o Models 481 and 482 -- disconnect -48 V dc power
from the terminal block.

2. Unplug all the cables connected to the hub you will
swap. If not already done, be sure to label the
cables so that you will know where to replug them.

If it will be more than a couple of minutes before
you replace the 8224, bypass the 8224 you are
swapping by connecting one of the hub expansion
cables between the 8224s above and below the 8224 you
are replacing.

3. If the 8224 you are removing from the stack has an
MEP module, remove it from its slot and then insert
it into the replacement 8224.

NOTE: Make sure the power to an 8224 is switched OFF
before you remove or install its MEP module.

4. Connect the cables to the ports in the replacement
8224.

5. Set the Uplink switch to match that of the replaced
8224.

6. Reconnect power to the rear of the unit.

7. Switch the 8224 ON.

8. Look for the following LED blink sequence:

o First, the 10BASE-T port LEDs should blink in
patterns of green, and then orange (for 5
seconds).

o Then, the LEDs beside the MEP should blink green,
and then orange (for 2 seconds).

o Then, the OK LED should turn orange (for 30
seconds).

o Finally, the OK LED should turn green.

9. If the OK LED is green, the 8224 is working
correctly.

If the OK LED is not green, the 8224 is not working
correctly. See Appendix G, "Help and Service
Information" for instructions.

4-2 8224 Ethernet Stackable Hub

PARTS
_____

The following table gives the part numbers for
replacement parts.

+-------------------------------------------------------+
| Table 4-1. Parts List |
+--------------+-------------------------+--------------+
| ITEM NUMBER | PART NAME | PART NUMBER |
+--------------+-------------------------+--------------+
| 1 | 8224 Model 001 | 73G9751 |
+--------------+-------------------------+--------------+
| 1 | 8224 Model 002 | 73G9761 |
+--------------+-------------------------+--------------+
| 2 | Module, media expansion | 73G9730 |
| | port (AUI) | |
+--------------+-------------------------+--------------+
| 2 | Module, media expansion | 73G9731 |
| | port (10BASE2) | |
+--------------+-------------------------+--------------+
| 2 | Module, media expansion | 73G9732 |
| | port (FOIRL/10BASE-FL) | |
+--------------+-------------------------+--------------+
| 3 | Bracket, rack mounting | 92G8547 |
+--------------+-------------------------+--------------+
| 4 | Screw, rack mounting | 92G8546 |
| | bracket | |
+--------------+-------------------------+--------------+
| 5 | Cable management | 92G8549 |
| | bracket | |
+--------------+-------------------------+--------------+
| 6 | Cable, hub expansion, | 73G9759 |
| | 6-inch | |
+--------------+-------------------------+--------------+
| not shown | Power cord, ac, | 13F9968 |
| | shielded (Models 001 | |
| | and 002 only) | |
+--------------+-------------------------+--------------+
| not shown | Special 19-in. bracket | 38H6969 |
| | kit (Models 481 and 482 | |
| | only) | |
+--------------+-------------------------+--------------+
| not shown | Special 23-in. bracket | 38H6970 |
| | kit (Models 481 and 482 | |
| | only) | |
+--------------+-------------------------+--------------+

NOTE: The label on the right, front corner of the unit
indicates the model number.

Figure 4-1. 8224 Parts

Chapter 4. Servicing 8224s 4-3

4-4 8224 Ethernet Stackable Hub

APPENDIX A. PLANNING CHARTS
____________________________

This appendix includes the following planning charts:

o Rack Inventory Chart
o IBM 8224 Stack Chart
o IBM 8224 Setup and Cabling Chart

You are encouraged to make as many copies of these charts
as you need. If you keep records on computer, you may
use these charts as formatting guidelines. See "Filling
Out the Planning Charts" on page 1-20 for instructions.

Figure A-1. Rack Inventory Chart

Figure A-2. IBM 8224 Stack Chart

Figure A-3. IBM 8224 Setup and Cabling Chart

A-2 8224 Ethernet Stackable Hub

APPENDIX B. CABLE PINOUT DIAGRAMS
__________________________________

Cable printout diagrams for straight-through 10BASE-T
cables, crossover 10BASE-T cables, and hub expansion
cables are shown in Figure B-1 through Figure B-8 on
page B-2.

STRAIGHT-THROUGH 10BASE-T CABLES

10BASE-T connections to devices such as workstations and
servers require straight-through cables, as shown
schematically in Figure B-1 and Figure B-2 for UTP, and
Figure B-3 for STP.

Two standards are shown for wiring UTP connectors, T568-A
and T568-B. The only difference between them is in the
color of the insulation.

Figure B-1. Straight-Through UTP Cable (RJ-45 to RJ-45),
T568-A

Figure B-2. Straight-Through UTP Cable (RJ-45 to RJ-45),
T568-B

Figure B-3. Straight-Through STP Cable (RJ-45 to IBM
Data Connector)

CROSSOVER 10BASE-T CABLES

Crossover cables are typically required when making
________________
10BASE-T connections to other hubs. The 8224 does not
require crossover cables, but if you need them,
_______
Figure B-4 through Figure B-6 on page B-2 show you how to
wire the connectors.

Two standards are shown for wiring UTP connectors, T568-A
and T568-B. The only difference between them is in the
color of the insulation.

Figure B-4. Crossover UTP Cable (RJ-45 to RJ-45), T568-A

Figure B-5. Crossover UTP Cable (RJ-45 to RJ-45), T568-B

Figure B-6. Crossover STP Cable (RJ-45 to IBM Data
Connector)

HUB EXPANSION CABLE

The hub expansion cable is a four-pair, straight-through
cable, wired as shown.

Two standards are shown for wiring hub expansion cable
connectors, T568-A in Figure B-7 and T568-B in Figure B-8
The only difference between them is in the color of the
insulation.

Figure B-7. Hub Expansion Cable, T568-A

Figure B-8. Hub Expansion Cable, T568-B

B-2 8224 Ethernet Stackable Hub

APPENDIX C. VALIDATING IP AND NETMASK ADDRESSES
________________________________________________

If you plan to manage a stack of 8224s through the Com
port of one of the 8224s, there are a number of rules you
must follow in assigning IP addresses and subnet masks to
the Com port. The Com port should be assigned an IP
address different from that of the 8224, and the logical
ANDing of the Com port's IP address and subnet mask must
be different from the logical ANDing of the 8224's
primary IP address and subnet mask.

The following sections explain the format of these
addresses and how to logically AND IP addresses and
subnet masks.

CONVERTING BETWEEN DECIMAL AND BINARY VALUES

IP addresses are typically expressed as 4 decimal values
separated by periods, like this: "9.67.83.254". This
format is called dotted-decimal.
______________

Each of the 4 decimal values represents an 8-bit binary
number called an octet.
_____

Position 8 7 6 5 4 3 2 1
Octet b b b b b b b b
Multiplier 128 64 32 16 8 4 2 1

Each binary digit ("b") has a value of 1 or 0. Each
position in the binary number has a multiplier as shown
above. The decimal equivalent of a binary number is
obtained by adding the multiplier values of the bit
positions that contain a 1.

For example,

0 0 0 0 1 0 0 1

in decimal is 9, since

8 + 1 = 9

To convert from decimal to a binary octet, assign a 1 in
the position with the largest value that can be
subtracted from the decimal value and still leave a
positive number. Subtract the multiplier of that
position from the decimal value. Repeat the process
until you cannot subtract from the remaining decimal

value. All bit positions that are not assigned a 1 are
assigned a 0.

Decimal 83 converts to a binary octet as follows:

The largest multiplier that can be subtracted from 83 and
still leave a positive value is 64, which occupies
position 7 in the octet.

0 1 b b b b b b

Subtract 64 from 83, leaving 19. Repeat the process,
subtracting 16 and assigning a 1 in position 5.

0 1 0 1 b b b b

This leaves 3. Assign 1s in positions 2 and 1. Thus 83
converts to:

0 1 0 1 0 0 1 1

LOGICALLY ANDING AN IP ADDRESS AND A SUBNET MASK

To logically AND an IP address and a subnet mask, convert
both to binary octets, and then multiply each column of
bits, as shown in this example:

IP ADDRESS 9.67.83.254
SUBNET MASK 255.255.255.0

In binary they appears as:

00001001 01000011 01010011 11111110 (IP address)
11111111 11111111 11111111 00000000 (Subnet mask)
-------- -------- -------- --------
00001001 01000011 01010011 00000000 (Product of each column)

This product is the logical AND of the two addresses.
Converting the binary octets of the logical AND back to
dotted-decimal notation yields: 9.67.83.0.

C-2 8224 Ethernet Stackable Hub

APPENDIX D. THE IBM 8224 MANAGEMENT INFORMATION BASE
_____________________________________________________

NOTE: A copy of the latest IBM 8224 MIB can be obtained
through the IBM Personal Computer Company BBS. Follow
the steps in "Getting New Microcode" on page 3-6,
substituting IBM8224.MIB for 8224_ddd.exe when you search
___________ ____________
for the file. The MIB you receive is not compressed and
is not an executable file. Therefore, it is not
necessary to perform step 5 of the procedure on page 3-6.

IBM-8224-MIB DEFINITIONS ::= BEGIN

-- May 21, 1996
-- The IBM 8224 product supports the following standard MIBs:
-- RFC1213 (MIB II)
-- System Group
-- Interfaces Group
-- Address Translation Group
-- IP Group
-- ICMP Group
-- UDP Group
-- SNMP Group
-- RFC1516 - Definitions of Managed Objects for IEEE 802.3 Repeater Devices
-- In addition, the 8224 supports the objects defined in this MIB.

IMPORTS
enterprises, Counter, IpAddress FROM RFC1155-SMI
DisplayString FROM RFC1213-MIB
OBJECT-TYPE FROM RFC-1212;

ibm OBJECT IDENTIFIER ::= { enterprises 2 }
ibmProd OBJECT IDENTIFIER ::= { ibm 6 }
ibm8224 OBJECT IDENTIFIER ::= { ibmProd 39 }
ibm8224NmmInfo OBJECT IDENTIFIER ::= { ibm8224 1 }
ibm8224StackInfo OBJECT IDENTIFIER ::= { ibm8224 2 }
ibm8224ExtendedPortInfo OBJECT IDENTIFIER ::= { ibm8224 3 }
ibm8224BkUpPortInfo OBJECT IDENTIFIER ::= { ibm8224 4 }
ibm8224IPTrapInfo OBJECT IDENTIFIER ::= { ibm8224 5 }
ibm8224IPXTrapInfo OBJECT IDENTIFIER ::= { ibm8224 6 }
ibm8224DownloadInfo OBJECT IDENTIFIER ::= { ibm8224 7 }
ibm8224Summary-group OBJECT IDENTIFIER ::= { ibm8224 8 }
ibm8224ExtendedRptrInfo OBJECT IDENTIFIER ::= { ibm8224 9 }
ibm8224IntrusionPortInfo OBJECT IDENTIFIER ::= { ibm8224 10 }

IpxAddress ::= OCTET STRING (SIZE(12))

--
-- The ibm8224NmmInfo Group
--

ibm8224ModuleDescr OBJECT-TYPE
SYNTAX DisplayString(SIZE(0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The text description of the module. Includes microcode revision level."
::= { ibm8224NmmInfo 1 }

ibm8224HwVer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The hardware version level."
::= { ibm8224NmmInfo 2 }

ibm8224FwMajorVer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The major number of the microcode version. For example, if the
microcode version is 2.12, the value of this object would be 2."
::= { ibm8224NmmInfo 3 }

ibm8224FwMinorVer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The minor number of the microcode version. For example, if the
microcode version is 2.12, the value of this object would be 12."
::= { ibm8224NmmInfo 4 }

ibm8224ThisNmm OBJECT-TYPE
SYNTAX INTEGER(1..10)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The stack index of the SNMP agent controlling this MIB. This corresponds
to an entry in ibm8224StackTable. The topmost module in the stack has a
stack index of 1."
::= { ibm8224NmmInfo 5 }

ibm8224WriteCommunity OBJECT-TYPE
SYNTAX DisplayString(SIZE(1..20))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The write community name FOR ALL MODULES IN THE STACK. If the value

D-2 8224 Ethernet Stackable Hub

is not public, the write community name is not returned for get
requests which do not have a matching community name. Note that the
write community name is automatically propagated to all of the other
modules in the stack."
::= { ibm8224NmmInfo 6 }

ibm8224WriteProtected OBJECT-TYPE
SYNTAX INTEGER
{
rw(1), -- the 8224 mib extensions are read/write
ro(2) -- the 8224 mib extensions are read only
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"When set to ro(2); read-only, the entire MIB, with the exception of this
object is made read only. This can be used in conjunction with a write
community name other than public for additional security. THIS OBJECT
APPLIES TO ALL MODULES IN THE STACK. Note that the value for
ibm8224WriteProtected is automatically propogated to all of the other
modules in the stack."
::= { ibm8224NmmInfo 7 }

ibm8224BootpRarpRequests OBJECT-TYPE
SYNTAX INTEGER
{
do-Bootp-Rarp(1), -- do bootp and rarp requests if no ip address
no-Bootp-Rarp(2) -- no bootp and rarp requests if no ip address
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"If the hub does not have an IP address assignment it periodically
attempts to find one via the BootP and RARP protocols. Setting
this object to no-Bootp-Rarp(2) disables this process. This would
be desirable, for instance, in an SNMP over IPX only network, where
the hub will never be assigned an IP address.

If Boot v1.02 or lower is installed, this object has no effect on
BootP/RARP use during the power up phase: it is always performed.
If Boot v1.30 or higher is installed, this object can disable
BootP/RARP for all phases of operation, including power up.

BootP can also be used to download firmware into the hub's flash
memory. If the flash firmware is invalid (perhaps due to an
unsuccessful previous download), the power up phase can use BootP
to load a valid flash image. For Boot v1.02 or lower, invalid
flash code always causes BootP to be used to locate a flash image.
For Boot v1.30 or higher, setting this object to no-Bootp-Rarp(2) will
disable the BootP search. If BootP is disabled and flash is invalid,
the only way to download a valid flash image is via the COM port
with XMODEM.

This object defaults to do-Bootp-Rarp(1). The value of this object is

Appendix D. The IBM 8224 Management Information Base D-3

saved in non-volatile memory. DURABLE"
::= { ibm8224NmmInfo 8 }

ibm8224IPFrameType OBJECT-TYPE
SYNTAX INTEGER
{
ethernet-ii(1), -- unit is using Ethernet_II frame type
ieee-8022-snap(2) -- unit is using 802.3 with 802.2 SNAP frame type
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Except when the hub is booting up, it will communicate over IP using a
single frame type defining the type of network that the IP traffic is
running on: Ethernet_II or IEEE 802.2. When the hub is performing BOOTP,
it does not assume any frame type and will attempt to BOOTP over both
types. It will use the frame type that the first BOOTP response uses for
the rest of its communication. The frame type of the BOOTP response will
be stored by this object."
::= { ibm8224NmmInfo 9 }

ibm8224IPXFrameType OBJECT-TYPE
SYNTAX INTEGER
{
ethernet-ii(1), -- unit is using Ethernet_II frame type
ethernet-802-3-RAW(2), -- unit is using ethernet-802-3-RAW
ieee-8022(3), -- unit is using 802.3 with 802.2 frame type
ieee-8022-snap(4) -- unit is using 802.3 with 802.2 SNAP frame type
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The frame type over which IPX communication originating from the ibm8224
will take place. The unit will respond to a packet using the same frame
type as was used in the request. This frame type comes into effect on any
packet that is generated by the hub, not in response to another external
packet. An example is a Trap. DURABLE"
::= { ibm8224NmmInfo 10 }

ibm8224IPXSAPBroadcast OBJECT-TYPE
SYNTAX INTEGER
{
do-ipx-SAP-Broadcast(1), -- Generate SAP broadcasts
no-ipx-SAP-Broadcast(2) -- Disable SAP broacasts
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The hub will generate SAP broadcasts over IPX. This allows
the hub to be auto-discovered by NMS (NetWare Management System) and is
used to generate IPX traps. Setting this object to
do-ipx-SAP-Broadcast(1) will generate SAP broadcasts if a Novell server
is present on the network. By setting this object to

D-4 8224 Ethernet Stackable Hub

no-ipx-SAP-Broadcasts(2) the hub will not generate SAP broadcasts.
IPX traps will not be generated if this object is set to
no-ipx-SAP-Broadcasts(2). This object has no effect on other IPX
communication to the hub."
::= { ibm8224NmmInfo 11 }

ibm8224IPAutoDiscoveryState OBJECT-TYPE
SYNTAX INTEGER
{
do-not-discover(1), -- Unit will not send out ARPs for AutoDiscovery
discover(2) -- Unit will send out ARPs for AutoDiscovery
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object will allow a user to enable the unit to send out periodic
ICMP PINGs to ensure that the unit's IP Address is contained in the ARP
cache of its default gateway (if any!). If the user sets the state to
discover(2), then the unit will issue ICMP PINGs at a rate defined by
ibm8224PingPacketRate. If the user selects do-not-discover(1) then the
unit does not send any ICMP Pings and risks not being discovered
automaticlly by IP based management applications. The default value is
discover(2). DURABLE"
::= { ibm8224NmmInfo 12 }

ibm8224PingPacketRate OBJECT-TYPE
SYNTAX INTEGER (55..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object will determine the rate (in seconds) at which ICMP Pings
will be sent out by the unit to ensure that its IP Address remains in
the ARP cache of the unit's default gateway. This object is only useful
if ibm8224IPAutoDiscoveryState is set to discover(2). The default value
is 55 seconds. DURABLE"
::= { ibm8224NmmInfo 13 }

ibm8224NVRAMStatus OBJECT-TYPE
SYNTAX INTEGER
{
no-error(1), -- The Unit's NVRAM is operational
error(2) -- The Unit's NVRAM has failed
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object provides status information of the NVRAM for the unit.
If the value is error(2), status information will not be retained
after a power cycle."
::= { ibm8224NmmInfo 14 }

ibm8224rptrReset OBJECT-TYPE
SYNTAX INTEGER

Appendix D. The IBM 8224 Management Information Base D-5

{
no-reset(1),
reset(2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this object to reset(2) causes the unit to restart, as if
the unit was switched off and then back on. All counters are destroyed.
All configuration information is retained.

After receiving a request to set this variable to reset(2), the agent
is allowed to delay the reset for a short period. This is done to
respond to the SNMP set request."
::= { ibm8224NmmInfo 15 }

ibm8224BootpRarpRetries OBJECT-TYPE
SYNTAX INTEGER (1..10)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object will allow the user to set the number of BootP/RARP retries
that will be performed when the unit goes through its Boot sequence (unit
is reset or power cycled). This object is used in conjunction with the
ibm8224BootpRarpRetryInterval object. The default value will be 2 retries.
DURABLE"
::= { ibm8224NmmInfo 16 }

ibm8224BootpRarpRetryInterval OBJECT-TYPE
SYNTAX INTEGER (5..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object will allow the user to set the time period (in seconds)
after which a BootP/RARP attempt will time out and the unit may issue
another similar request. This object is used in conjunction with the
ibm8224BootpRarpRetries object. The default value will be 5 seconds.

ATTENTION: Remember that while the unit is booting up, no management will
be available so be careful in selecting the number of retries and the
interval for BootP/RARPs. DURABLE"
::= { ibm8224NmmInfo 17 }

ibm8224VT100ScreenRefresh OBJECT-TYPE
SYNTAX INTEGER (1..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object will determine the rate, in seconds, at which the VT100
screen will refresh the automatic fields (for example: statistics values).
The default value will be 5 seconds.
DURABLE"
::= { ibm8224NmmInfo 18 }

D-6 8224 Ethernet Stackable Hub

ibm8224ModemInitString OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..40))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object provides a Modem Initialization String input which will be
used to initialize a modem to the proper configuration. These are the
minimum parameters required:
Auto answer
number of rings
Baud Rate
Auto Detection method of Baud rate connection string if supported
by the modem is recommended
The default string is the following:

AT&FX1E0Q0V1&C1S0=1S12=5

DURABLE."
::= { ibm8224NmmInfo 19 }

ibm8224ModemAutoNegotiateState OBJECT-TYPE
SYNTAX INTEGER
{
enabled(1), -- enable modem auto-negotiate
disabled(2) -- disable modem auto-negotiate
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"If enabled(1), then the ibm8224 will adjust its speed to that specified
when the modem answers the incoming connection. If the modem is
configured by either ibm8224ModemInitString or the DIP switches on the
modem for variable-speed connection rates, this object should be set to
enabled(1). If it is to disabled(2), then no adjustment is made for baud
rate differences. The disabled(2) choice is for modems that do not support
variable connection rates between the modem and the ibm8224 or modems
that have been configured for fixed serial port rates via the
ibm8224ModemInitString object.
DURABLE."
::= { ibm8224NmmInfo 20 }

ibm8224SlipIpAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP Address of the SLIP Interface over which the Management Software
may be communicating. DURABLE"
::= { ibm8224NmmInfo 21 }

ibm8224SlipIpNetMask OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory

Appendix D. The IBM 8224 Management Information Base D-7

DESCRIPTION
"The IP Subnet Mask of the SLIP Interface over which the Management
Software may be communicating. DURABLE"
::= { ibm8224NmmInfo 22 }

ibm8224AutoPolarityReversal OBJECT-TYPE
SYNTAX INTEGER
{
disable(1), -- disable auto polarity reversal
enable(2) -- enable auto polarity reversal
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The unit's ability to detect and reverse the polarity on the receive
lines of all UTP ports can be enabled or disabled. DURABLE."
::= { ibm8224NmmInfo 23 }

--
-- The ibm8224StackInfo Group
--
-- This group contains the information which can be shared among all
-- of the modules in the stack.
--

ibm8224StackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IBM8224StackEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The stack configuration table."
::= { ibm8224StackInfo 1 }

ibm8224StackEntry OBJECT-TYPE
SYNTAX IBM8224StackEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"There is one entry for each module in the stack."
INDEX { ibm8224StackIndex }
::= { ibm8224StackTable 1 }

IBM8224StackEntry ::= SEQUENCE {
ibm8224StackIndex
INTEGER,
ibm8224ModuleType
INTEGER,
ibm8224BkplNum
INTEGER,
ibm8224PhysAddr
OCTET STRING,
ibm8224IpAddr
IpAddress,
ibm8224IpDefaultGateway

D-8 8224 Ethernet Stackable Hub

IpAddress,
ibm8224IpNetMask
IpAddress,
ibm8224Reset
INTEGER
}

ibm8224StackIndex OBJECT-TYPE
SYNTAX INTEGER(1..10)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The position of this module in the stack. The topmost module in the
stack is numbered 1."
::= { ibm8224StackEntry 1 }

ibm8224ModuleType OBJECT-TYPE
SYNTAX INTEGER
{
empty(1), -- nothing installed
ibm224-2(2), -- 16 port, RJ45, managed
ibm8224-2-a(3), -- 16 port, RJ45, 1 AUI, managed
ibm8224-2-b(4), -- 16 port, RJ45, 1 BNC, managed
ibm8224-2-f(5), -- 16 port, RJ45, 1 fiber, managed
ibm8224-2-mu(6), -- 16 port, RJ45, 1 MIS UTP managed
ibm8224-2-ma(7), -- 16 port, RJ45, 1 MIS AUI, managed
ibm8224-2-mb(8), -- 16 port, RJ45, 1 MIS BNC, managed
ibm8224-2-mf(9), -- 16 port, RJ45, 1 MIS fiber, managed
ibm8224-1(52), -- 16 port, RJ45, unmanaged
ibm8224-1-a(53), -- 16 port, RJ45, 1 AUI, unmanaged
ibm8224-1-b(54), -- 16 port, RJ45, 1 BNC, unmanaged
ibm8224-1-f(55), -- 16 port, RJ45, 1 fiber, unmanaged
ibm8224-1-mu(56), -- 16 port, RJ45, 1 MIS UTP, unmanaged
ibm8224-1-ma(57), -- 16 port, RJ45, 1 MIS AUI, unmanaged
ibm8224-1-mb(58), -- 16 port, RJ45, 1 MIS BNC, unmanaged
ibm8224-1-mf(59), -- 16 port, RJ45, 1 MIS fiber, unmanaged
unknown(1000) -- Unknown module type
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of module."
::= { ibm8224StackEntry 2 }

ibm8224BkplNum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The number of the backplane to which the module is connected. A module
can be either connected to the Ethernet backplane (value = 1) or be
isolated from it (value = 6)."
::= { ibm8224StackEntry 3 }

Appendix D. The IBM 8224 Management Information Base D-9

ibm8224PhysAddr OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The physical (MAC) address of the module."
::= { ibm8224StackEntry 4 }

ibm8224IpAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The internet address of the SNMP agent for this module. This object
allows an SNMP manager to determine and set the IP addresses of each
agent in the stack. Setting a new IP address through this object does
not take effect until ibm8224Reset is set to reset(2)."
::= { ibm8224StackEntry 5 }

ibm8224IpDefaultGateway OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The internet address of the default IP gateway for this module. This
object allows an SNMP manager to determine and set the IP default
gateway addresses of each agent in the stack. Setting a new IP default
gateway through this object does not take effect until ibm8224Reset is
set to reset(2)."
::= { ibm8224StackEntry 6 }

ibm8224IpNetMask OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The internet network mask of the default IP gateway for this module. This
object allows an SNMP manager to determine and set the IP network masks
of each agent in the stack. Setting a new IP net mask through this
object does not take effect until ibm8224Reset is set to reset(2)."
::= { ibm8224StackEntry 7 }

ibm8224Reset OBJECT-TYPE
SYNTAX INTEGER
{
notreset(1), -- not resetting
reset(2) -- reset
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"When set to reset(2), the settings for ibm8224IpAddr, ibm8224IpNetMask,
and ibm8224IpDefaultGateway are made to take effect."
::= { ibm8224StackEntry 8 }

D-10 8224 Ethernet Stackable Hub

--
-- The ibm8224ExtendedPortInfo Group
--

ibm8224ExtendedPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF IBM8224ExtendedPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table has one entry for each port defined."
::= { ibm8224ExtendedPortInfo 1 }

ibm8224ExtendedPortEntry OBJECT-TYPE
SYNTAX IBM8224ExtendedPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Defines per-port information."
INDEX { ibm8224ExtendedPortId }
::= { ibm8224ExtendedPortTable 1 }

IBM8224ExtendedPortEntry ::= SEQUENCE {
ibm8224ExtendedPortId
INTEGER,
ibm8224ExtendedPortLinkTestEnable
INTEGER,
ibm8224ExtendedPortLinkState
INTEGER,
ibm8224ExtendedPortPolarityState
INTEGER
}

ibm8224ExtendedPortId OBJECT-TYPE
SYNTAX INTEGER(1..17)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Uniquely identifies the port for which this entry contains information."
::= { ibm8224ExtendedPortEntry 1 }

ibm8224ExtendedPortLinkTestEnable OBJECT-TYPE
SYNTAX INTEGER
{
enable(1),
disable(2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Defines whether or not Link Test is enabled for the port."
::= { ibm8224ExtendedPortEntry 2 }

ibm8224ExtendedPortLinkState OBJECT-TYPE

Appendix D. The IBM 8224 Management Information Base D-11

SYNTAX INTEGER
{
linkDown(1),
linkUp(2),
notApplicable(3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value indicating the current state of the link attached to the port.
The possible values are:

linkDown(1) The link pulses are not being received by the port.
linkUp(2) The link pulses are being received by the port.
notApplicable(3) The port is an AUI or other non-10BaseT port."
::= { ibm8224ExtendedPortEntry 3 }

ibm8224ExtendedPortPolarityState OBJECT-TYPE
SYNTAX INTEGER
{
unknown(1),
polarityReversed(2),
notApplicable(3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value indicating the current state of the receive line auto polarity
reversal on the port. The possible values are:

unknown(1) The polarity is not reversed on the port or the
function is not enabled.
polarityReversed(2) The receive line polarity is currently reversed
on the port.
notApplicable(3) The port is an AUI or other non-10BaseT port."

::= { ibm8224ExtendedPortEntry 4 }

--
-- The ibm8224BkUpPortInfo Group
--

ibm8224BkUpPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF IBM8224BkUpPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table has one entry for each backup port defined."
::= { ibm8224BkUpPortInfo 1 }

ibm8224BkUpPortEntry OBJECT-TYPE
SYNTAX IBM8224BkUpPortEntry
ACCESS not-accessible
STATUS mandatory

D-12 8224 Ethernet Stackable Hub

DESCRIPTION
"Defines the backup ports."
INDEX { ibm8224BkUpPortId }
::= { ibm8224BkUpPortTable 1 }

IBM8224BkUpPortEntry ::= SEQUENCE {
ibm8224BkUpPortId
INTEGER,
ibm8224BkUpPortBackupPort
INTEGER,
ibm8224BkUpPortBackupEnable
INTEGER
}

ibm8224BkUpPortId OBJECT-TYPE
SYNTAX INTEGER(1..17)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Uniquely identifies the port for which this entry contains information."
::= { ibm8224BkUpPortEntry 1 }

ibm8224BkUpPortBackupPort OBJECT-TYPE
SYNTAX INTEGER(1..17)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The port number of the backup port for this port. A value of 0
indicates that no backup is specified."
::= { ibm8224BkUpPortEntry 2 }

ibm8224BkUpPortBackupEnable OBJECT-TYPE
SYNTAX INTEGER
{
none(1), -- No backup is specified.
enable(2), -- Monitoring of primary port is enabled. Backup port
-- is partitioned.
disable(3), -- Monitoring of primary port is disabled.
tripped(4) -- The backup port has taken over for the primary port.
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The status of the backup port specified by ibm8224BkUpPortBackupPort.
The port being monitored is termed the primary port and is specified
by ibm8224BkUpPortId. Writing enable(2) to this object enables monitoring
of the primary port. This means that the backup port is partitioned,
and remains partitioned until an event occurs which causes the backup
port to take over for the primary port. Writing disable(3) to this
object disables monitoring; it enables the backup port. Writing
none(1) to this object deletes the entry from the table.

For a 10BaseT primary port, a backup port will take over if the primary
port loses link pulse or auto-partitions. For an AUI primary port, a

Appendix D. The IBM 8224 Management Information Base D-13

backup port will take over if the primary port auto-partitions."
::= { ibm8224BkUpPortEntry 3 }

--
-- The ibm8224IPTrapInfo Group
--

ibm8224IPTrapReceiverTable OBJECT-TYPE
SYNTAX SEQUENCE OF IBM8224IPTrapReceiverEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The table containing the IP addresses of SNMP managers that are
to receive traps. To set an entry in the table, perform a set of
ibm8224IPTrapReceiverComm.<IP address of SNMP manager> to the community
name to be used in the trap. To delete an entry, set
ibm8224IPTrapType.<IP address of SNMP manager> to invalid(2)."
::= { ibm8224IPTrapInfo 1 }

ibm8224IPTrapReceiverEntry OBJECT-TYPE
SYNTAX IBM8224IPTrapReceiverEntry
ACCESS not-accessible
STATUS mandatory
INDEX { ibm8224IPTrapReceiverAddr }
::= { ibm8224IPTrapReceiverTable 1 }

IBM8224IPTrapReceiverEntry ::= SEQUENCE {
ibm8224IPTrapType
INTEGER,
ibm8224IPTrapReceiverAddr
IpAddress,
ibm8224IPTrapReceiverComm
DisplayString
}

ibm8224IPTrapType OBJECT-TYPE
SYNTAX INTEGER
{
other (1), -- none of the following (i.e., a valid entry)
invalid (2) -- an invalidated address
}
ACCESS read-write
STATUS mandatory
::= { ibm8224IPTrapReceiverEntry 1 }

ibm8224IPTrapReceiverAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
::= { ibm8224IPTrapReceiverEntry 2 }

ibm8224IPTrapReceiverComm OBJECT-TYPE
SYNTAX DisplayString(SIZE(1..20))
ACCESS read-write

D-14 8224 Ethernet Stackable Hub

STATUS mandatory
::= { ibm8224IPTrapReceiverEntry 3 }

--
-- The ibm8224IPXTrapInfo Group
--

ibm8224IPXTrapReceiverTable OBJECT-TYPE
SYNTAX SEQUENCE OF IBM8224IPXTrapReceiverEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The table containing the IPX addresses of SNMP managers that are
to receive traps. To set an entry in the table, perform a set of
ibm8224IPXTrapReceiverComm.<IPX address of SNMP manager> to the community
name to be used in the trap. To delete an entry, set
ibm8224IPXTrapType.<IPX address of SNMP manager> to invalid(2)."
::= { ibm8224IPXTrapInfo 1 }

ibm8224IPXTrapReceiverEntry OBJECT-TYPE
SYNTAX IBM8224IPXTrapReceiverEntry
ACCESS not-accessible
STATUS mandatory
INDEX { ibm8224IPXTrapReceiverAddr }
::= { ibm8224IPXTrapReceiverTable 1 }

IBM8224IPXTrapReceiverEntry ::= SEQUENCE {
ibm8224IPXTrapType
INTEGER,
ibm8224IPXTrapReceiverAddr
IpxAddress,
ibm8224IPXTrapReceiverComm
DisplayString
}

ibm8224IPXTrapType OBJECT-TYPE
SYNTAX INTEGER
{
other (1), -- none of the following (that is a valid entry)
invalid (2) -- an invalidated address
}
ACCESS read-write
STATUS mandatory
::= { ibm8224IPXTrapReceiverEntry 1 }

ibm8224IPXTrapReceiverAddr OBJECT-TYPE
SYNTAX IpxAddress
ACCESS read-write
STATUS mandatory
::= { ibm8224IPXTrapReceiverEntry 2 }

ibm8224IPXTrapReceiverComm OBJECT-TYPE
SYNTAX DisplayString(SIZE(1..20))

Appendix D. The IBM 8224 Management Information Base D-15

ACCESS read-write
STATUS mandatory
::= { ibm8224IPXTrapReceiverEntry 3 }

--
-- The ibm8224DownloadInfo Group
--

ibm8224DownloadImagePathname OBJECT-TYPE
SYNTAX DisplayString(SIZE(64))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The fully qualified pathname of the image file to download. Please
refer to the description of ibm8224DownloadState. The name is a fully
qualified pathname. On DOS and OS/2 systems this should include a drive
letter."
::= { ibm8224DownloadInfo 1 }

ibm8224DownloadServerIp OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP address of the machine which is to download the agent. Please
refer to the description of ibm8224DownloadState."
::= { ibm8224DownloadInfo 2 }

ibm8224DownloadImageVersion OBJECT-TYPE
SYNTAX DisplayString(SIZE(9))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The version name of the the image file to download."
::= { ibm8224DownloadInfo 3 }

ibm8224DownloadState OBJECT-TYPE
SYNTAX INTEGER
{
notDownloading(1),
downloading(2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this object to downloading(2) intiates a TFTP download of the
agent from the server specified by ibm8224DownloadServerIp. The object
ibm8224DownloadImagePathname specifies the image file to download. The
name is a fully qualified pathname. On DOS and OS/2 systems this should
include a drive letter."
::= { ibm8224DownloadInfo 4 }

D-16 8224 Ethernet Stackable Hub

-- The Summary groups provide a performance improvement for a network manager
-- when retrieving port information. They combine information from various
-- objects into one large octet string.

ibm8224GroupPortSummary OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(51..54))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A summary of port information. It consists of the following information:

Repeater operational status (1)
Group operational status (1)
Number of port infos following (1)
For each port:
Port admin state (1)
Port link state (1)
Port partition state (1)"
::= { ibm8224Summary-group 1 }

ibm8224PortAddrSummary OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(96..102))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A summary of MAC Address per port. Note: the MAC address is the last
MAC address that was detected on the port.

The summary consists of the following addresses:
Port 1 MAC address (6)
Port 2 MAC address (6)
...
Port 17 MAC Address (6)"
::= { ibm8224Summary-group 2 }

ibm8224PortCtrSummary OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(52))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A summary of RFC1516 port monitor counters for the port
specified by ibm8224PortCtrSummaryCtl.

The summary consists of the following counters:
rptrMonitorPortGroupIndex (4)
rptrMonitorPortIndex (4)
rptrMonitorPortReadableFrames (4)
rptrMonitorPortReadableOctets (4)
rptrMonitorPortFCSErrors (4)
rptrMonitorPortAlignmentErrors (4)
rptrMonitorPortFrameTooLongs (4)
rptrMonitorPortShortEvents (4)
rptrMonitorPortRunts (4)
rptrMonitorPortCollisions (4)

Appendix D. The IBM 8224 Management Information Base D-17

rptrMonitorPortLateEvents (4)
rptrMonitorPortVeryLongEvents (4)
rptrMonitorPortDataRateMismatches (4)"
::= { ibm8224Summary-group 3 }

ibm8224PortCtrSummaryCtl OBJECT-TYPE
SYNTAX INTEGER(1..17)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Specifies the port for the counter summary retrieval."
::= { ibm8224Summary-group 4 }

--
-- The ibm8224ExtendedRptrInfo Group
--
-- This group contains performance monitoring statistics for the repeater
-- which are not found in RFC1516. Each counter is a summary of a statisitc
-- for all of the ports in the repeater.
--

ibm8224ExtendedRptrFCSErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Increment Counter by one for each frame with FCSError and without
FramingError and whose OctetCount is greater than or equal to
minFrameSize and less than or equal to maxFrameSize.

Note: The approximate minimum time between Counter rollovers is
81 hours."
::= { ibm8224ExtendedRptrInfo 1 }

ibm8224ExtendedRptrAlignmentErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Increment Counter by one for each frame with FCSError and FramingError
and whose octetCount is greater than or equal to minFrameSize and less
than or equal to maxFrameSize.

Note: The approximate minimum time between Counter rollovers is 81
hours."
::= { ibm8224ExtendedRptrInfo 2 }

ibm8224ExtendedRptrFramesTooLong OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Increment Counter by one for each frame whose OctetCount is greater
than maxFrameSize.

D-18 8224 Ethernet Stackable Hub

Note: The approximate minimum time between Counter rollovers is 61
days."
::= { ibm8224ExtendedRptrInfo 3 }

ibm8224ExtendedRptrShortEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Increment Counter by one for each carrier event whose ActivityDuration
is greater than ShortEventMinTime and less than ShortEventMaxTime.
ShortEventMinTime represents any event of sufficient duration to initiate
transmission by a repeater. ShortEventMaxTime is greater than 7.4uS and
less than 8.2uS. ShortEventMaxTime has tolerances included to provide
for circuit losses between a conformance test point at the AUI and the
measurement point within the state machine.

Note: shortEvents might indicate an externally generated noise hit which
will cause the relay to transmit Runts to its other ports, or propagate
a collision (which may be late) back to the transmitting DTE and damaged
frames to the rest of the network. Such shortEvents are not a feature of
normal network activity. Also it should be noted that a MAU that is
attached to a coax segment might have several carrier dropouts on the DI
circuit before the CI circuit is active and stable. Such dropouts will
increment the shortEvent Counter but are considered normal for a coax
segment."
::= { ibm8224ExtendedRptrInfo 4 }

ibm8224ExtendedRptrRunts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Increment Counter by one for each carrier event whose ActivityDuration
is greater than ShortEventMaxTime and less than RuntMaxTime.
RuntMaxTime is greater than 53.2uS and less than 56.0uS.

An event whose length is greater than 7.4uS but less than 8.2uS shall
increment either the ShortEvent object or the Runts object but not both.

A non-collision event greater than 53.2uS but less than 56.0uS may or may
not be counted as a runt. A non-collision event greater than or equal to
56.0uS shall not be counted as a runt. RuntMaxTime has tolerances included
to provide for circuit losses between a conformance test point at the AUI
and the measurement point within the state machine.

Note: Runts do not indicate a problem in the network. The approximate
minimum time for Counter rollover is 16 hours."
::= { ibm8224ExtendedRptrInfo 5 }

ibm8224ExtendedRptrLateEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only

Appendix D. The IBM 8224 Management Information Base D-19

STATUS mandatory
DESCRIPTION
"Increment Counter by one for each carrier event in which the CollIn(X)
variable transitions to the value SQE while the activity duration is
greater than the LateEventThreshold. Such a carrier event is counted
twice, as both a Collision and as a LateEvent. The LateEventThreshold
is greater than 480 bit times less than 565 bit times. LateEventThreshold
has tolerances included to permit an implementation to build a single
threshold to serve as both the LateEventThreshold and ValidPacketMinTime
threshold.

Note: The approximate minimum time between Counter rollovers is 81
hours."
::= { ibm8224ExtendedRptrInfo 6 }

ibm8224ExtendedRptrVeryLongEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The veryLongEvents object counts the number of times a packet has been
received by this port that was so long that the repeater was forced to
go into a jabber protection condition.

Note: The approximate minimum time for Counter rollover is 200 days."
::= { ibm8224ExtendedRptrInfo 7 }

ibm8224ExtendedRptrDataRateMismatches OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The dataRateMismatches object counts the number of times that a packet
has been received by this port with the transmission frequency
(data rate) detectably mismatched from the local transmit frequency. The
exact degree is implementation-specific and is to be defined by the
implementor for conformance testing.

Note: Whether or not the repeater was able to maintain data integrity is
beyond the scope of this standard."
::= { ibm8224ExtendedRptrInfo 8 }

--
-- The ibm8224IntrusionPortTable Group: For Port Level Intrusion SetUp. The
-- objects in this table will allow a user to set up Intrusion for any port
-- controlled by this unit.
--

ibm8224IntrusionPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF IBM8224IntrusionPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table has one entry for each port defined."

D-20 8224 Ethernet Stackable Hub

::= { ibm8224IntrusionPortInfo 1 }

ibm8224IntrusionPortEntry OBJECT-TYPE
SYNTAX IBM8224IntrusionPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table has one entry for each port defined. The index into the table
is ibm8224ExtendedPortId. For example, the value of the intrusion state
for port 12 is given by ibm8224IntrusuionPortStatus.12."
INDEX { ibm8224IntrusionPortId }
::= { ibm8224IntrusionPortTable 1 }

IBM8224IntrusionPortEntry ::= SEQUENCE {
ibm8224IntrusionPortId
INTEGER,
ibm8224IntrusionPortStatus
INTEGER,
ibm8224IntrusionPortMACAddress
OCTET STRING,
ibm8224IntrusionPortMACAddressStr
DisplayString
}

ibm8224IntrusionPortId OBJECT-TYPE
SYNTAX INTEGER (1..17)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Uniquely identifies the port for which this entry contains information."
::= { ibm8224IntrusionPortEntry 1 }

ibm8224IntrusionPortStatus OBJECT-TYPE
SYNTAX INTEGER
{
disable(1),
enable(2),
tripped(3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Defines whether Intrusion is disabled, enabled, or tripped. If
an IBM 8224-aware SNMP management application has enabled an additional
level of security authorization for intrusion, an attempt to set this
object might result in a PDU error. In this case, the SNMP management
application must be used to modify intrusion configuration."
::={ ibm8224IntrusionPortEntry 2 }

ibm8224IntrusionPortMACAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (6))
ACCESS read-write
STATUS mandatory
DESCRIPTION

Appendix D. The IBM 8224 Management Information Base D-21

"Defines the authorized MAC address for intrusion detection. All values
are legal. If an IBM 8224-aware SNMP management application has enabled
an additional level of security authorization for Intrusion, an attempt
to set this object might result in a PDU error. In this case, the SNMP
management application must be used to modify intrusion configuration."
::= { ibm8224IntrusionPortEntry 3 }

ibm8224IntrusionPortMACAddressStr OBJECT-TYPE
SYNTAX DisplayString (SIZE (12))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Defines the authorized MAC address for intrusion detection. If an IBM
8224-aware SNMP management application has enabled an additional level
of security authorization for Intrusion, an attempt to set this object
may result in a PDU error. In this case, the SNMP management application
must be used to modify intrusion configuration."
::= { ibm8224IntrusionPortEntry 4 }

END

D-22 8224 Ethernet Stackable Hub

APPENDIX E. ETHERNET FRAME FORMAT SUPPORT
__________________________________________

This appendix identifies and describes the Ethernet frame
formats supported by the 8224 for IP and IPX traffic.

FRAME FORMATS
_____________

There are two basic Ethernet frame formats:

o Ethernet Version 2 (II)

This format was defined by DEC, Intel, and Xerox, and
is often referred to as the DIX Ethernet format. It
has the format illustrated in Figure E-1.

The Format Type field defines the layout of the Data
field. For example, a Format Type of X'0800'
identifies an IP frame and X'8137' identifies a
Novell IPX frame. The length of the frame must be
obtained from the hardware or by interpreting the
frame data.

This frame format is identified in Novell NetWare as
Ethernet_II.
___________

Figure E-1. Ethernet II Frame Format

o IEEE 802.3

This format was defined by the IEEE and differs from
Ethernet II only in the two bytes preceding the Data
field. That is, Frame Type is replaced with Data
Length. This length is the length of the data field
only and does not include any of the other fields
(address, CRC, and so on). The format is illustrated
in Figure E-2 on page E-2.

This format is sometimes referred to as 802.3 Raw
since there is no provision for identification of
multiple protocols.

This frame format is identified in Novell NetWare as
Ethernet_802.3.
______________

Figure E-2. IEEE 802.3 Frame Format

EXTENDED ETHERNET FRAME FORMATS
_______________________________

In order to support multiple protocols within the basic
IEEE 802.3 format, two extended formats are defined:

o IEEE 802.3 with 802.2 LLC headers

The IEEE defines an 802.2 Logical Link Control (LLC)
header that appears in the first three bytes of the
802.3 Data field. When using the LLC header the
number of bytes available for data is reduced to
1 497. The format of the LLC header is illustrated
in Figure E-3.

The two Service Access Point (SAP) fields are used to
identify the type of protocol being used within the
frame. However, the small size of these fields (1
byte each) is usually insufficient to identify all of
the protocols that might be used in a large network.

This frame format is identified in Novell NetWare as
Ethernet_802.2.
______________

Figure E-3. 802.2 LLC Header

o IEEE 802.3 with 802.2 SNAP headers

The Sub-Network Access Protocol (SNAP) header extends
the LLC header with an additional five-byte Protocol
ID field. The total length of the SNAP header is
eight bytes and the available number of data bytes is
1 492. The format of the SNAP header is illustrated
in Figure E-4 on page E-3.

The presence of the Protocol ID field is indicated by
setting the DSAP and SSAP fields to X'AA' The first
three bytes of the Protocol ID field are zero. The
last two bytes contain the frame type identifier.
For example, the Protocol ID field is X'0000000800'
for an IP frame and X'0000008137' for an IPX frame.

E-2 8224 Ethernet Stackable Hub

This frame format is identified in Novell NetWare as
Ethernet_SNAP.
_____________

Figure E-4. 802.2 SNAP Header

SUPPORTED FRAME FORMATS
_______________________

8224 support for the frame formats described above is as
follows:

o IP traffic

- Ethernet II

- IEEE 802.3 with 802.2 SNAP headers

o IPX traffic

- Ethernet II

- IEEE 802.3

- IEEE 802.3 with 802.2 LLC headers

- IEEE 802.3 with 802.2 SNAP headers

Appendix E. Ethernet Frame Format Support E-3

E-4 8224 Ethernet Stackable Hub

APPENDIX F. NOTICES AND PRODUCT WARRANTY
_________________________________________

References in this publication to IBM products, programs,
or services do not imply that IBM intends to make these
available in all countries in which IBM operates. Any
reference to an IBM product, program, or service is not
intended to state or imply that only IBM's product,
program, or service may be used. Any functionally
equivalent product, program, or service that does not
infringe any of IBM's intellectual property rights may be
used instead of the IBM product, program, or service.
Evaluation and verification of operation in conjunction
with other products, except those expressly designated by
IBM, are the user's responsibility.

IBM may have patents or pending patent applications
covering subject matter in this document. The furnishing
of this document does not give you any license to these
patents. You can send license inquiries, in writing, to
the IBM Director of Licensing, IBM Corporation, 500
Columbus Avenue, THORNWOOD, NY 10594 USA.

ELECTRONIC EMISSION NOTICES
___________________________

FEDERAL COMMUNICATIONS COMMISSION (FCC) STATEMENT

NOTE: This equipment has been tested and found to comply
with the limits for a Class A digital device, pursuant to
Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful
interference when the equipment is operated in a
commercial environment. This equipment generates, uses,
and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction
manual, may cause harmful interference to radio
communications. Operation of this equipment in a
residential area is likely to cause harmful interference,
in which case the user will be required to correct the
interference at his own expense.

Properly shielded and grounded cables and connectors (IBM
part number 13F9968 or its equivalent) must be used in
order to meet FCC emission limits. IBM is not
responsible for any radio or television interference
caused by using other than recommended cables and
connectors or by unauthorized changes or modifications to
this equipment. Unauthorized changes or modifications
could void the user's authority to operate the equipment.

This device complies with Part 15 of the FCC Rules.
Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received,
including interference that may cause undesired
operation.

F-2 8224 Ethernet Stackable Hub

Industry Canada Class A Emission Compliance Statement

This Class A digital apparatus meets the requirements of
the Canadian Interference-Causing Equipment Regulations.

Avis de conformite aux normes d'Industrie Canada

Cet appareil numerique de la classe A respecte toutes les
exigences du Reglement sur le materiel brouilleur du
Canada.

Statement of Compliance with the United Kingdom Telecommunications Act 1984

This apparatus is approved under approval number
NS/G/1234/J/100003 for indirect connections to the public
telecommunications systems in the United Kingdom.

European Community (CE) Mark of Conformity Statement

This product is in conformity with the protection
requirements of EU Council Directive 89/336/EEC on the
approximation of the laws of the Member States relating
to electromagnetic compatibility. IBM cannot accept
responsibility for any failure to satisfy the protection
requirements resulting from a non-recommended
modification of the product, including the fitting of
non-IBM option cards.

This product has been tested and found to comply with the
limits for Class A Information Technology Equipment
according to CISPR 22/European Standard EN 55022. The
limits for Class A equipment were derived for commercial
and industrial environments to provide reasonable
protection against interference with licensed
communication equipment. WARNING: THIS IS A CLASS A
PRODUCT. IN A DOMESTIC ENVIRONMENT THIS PRODUCT MAY
CAUSE RADIO INTERFERENCE IN WHICH CASE THE USER MAY BE
REQUIRED TO TAKE ADEQUATE MEASURES.

Dieses Geraet ist berechtigt in Uebereinstimmung mit dem
deutschen EMVG vom 9.Nov.92 das EG-Konformitaetszeichen
zu fuehren. Der AuBteller der Konformitaetserklaerung
ist die IBM United Kingdom Laboratories Limited, Mail
Point 147, Hursley Park Winchester, Hampshire S021 2JN,
England.

Dieses Geraet erfuellt die Bedingungen der EN 55022
Klasse A. Fuer diese Klasse von Geraeten gilt folgende
Bestimmung nach dem EMVG: Geraete duerfen an Orten, fuer
die sie nicht ausreichend entstoert sind, nur mit
besonderer Genehmigung des Bundesminesters fuer Post und

Appendix F. Notices and Product Warranty F-3

Telekommunikation oder des Bundesamtes fuer Post und
Telekommunikation betrieben werden. Die Genehmigung wird
erteilt, wenn keine elektromagnetischen Stoerungen zu
erwarten sind. Auszug aus dem EMVG vom 9.Nov.92, Para.3,
Abs.4)

Hinwies:
________

Dieses Genehmigungsverfahren ist von der Deutschen
Bundespost noch nicht veroeffentlicht worden.

F-4 8224 Ethernet Stackable Hub

Japanese Voluntary Control Council for Interference (VCCI) Statement

This equipment is in the 1st Class category (information
equipment to be used in commercial and/or industrial
areas) and conforms to the standards set by the Voluntary
Control Council for Interference by Information
Technology Equipment aimed at preventing radio
interference in commercial and industrial areas.

Consequently, when used in a residential area or in an
adjacent area thereto, radio interference may be caused
to radios and TV receivers, etc.

Read the instructions for correct handling.

Appendix F. Notices and Product Warranty F-5

LITHIUM BATTERY NOTICE
______________________

LITHIUM BATTERY

This unit contains a non-replaceable lithium battery.
The unit should be returned to the nearest IBM-authorized
dealer for proper disposal.

PILE AU LITHIUM

Cette unite contient une pile au lithium non remplacable.
Pour la mise au rebut de cette pile, renvoyez l'unite a
votre partenaire commercial IBM.

LITIUMBATTERI

Denne enhed indeholder et litiumbatteri. Batteriet ma
ikke udskiftes. Enheden skal kasseres i overensstemmelse
med gaeldende miljobestemmelser for litiumbatterier.

DC POWER CABLES NOTICE
______________________

NOTE: The 8224 Models 481 and 482 power systems must be
connected to at least one -48 V dc power source which is
electrically isolated from its ac power source. In
addition, the -48 V dc power source is to be reliably
connected to earth (grounded).

A second dc source may also be added.

Power and ground wires used in the United States and
Canada should be listed by Underwriters Laboratories (UL)
and certified by the Canadian Standards Association
(CSA).

It is the responsibility of the installing organization
to provide all power wiring from the service fuse
location to the system unit using all appropriate
telephone company specifications. In addition, the
following requirements must be met:

1. Both -48 V power and return leads must be 20 AWG
minimum and 12 AWG maximum.

2. The -48 V power lead must be a fused lead with a fuse
not to exceed 2 A for each feed.

F-6 8224 Ethernet Stackable Hub

TRADEMARKS
__________

The following terms in this publication, are trademarks
of IBM Corporation in the United States or other
countries or both:

HelpCenter OS/2
HelpWare Personal System/2
IBM StackWatch
NetView System/370
Operating System/2

Windows is a trademark or a registered trademark of
Microsoft Corporation.

Other company, product, and service names may be
trademarks or service marks of others.

Appendix F. Notices and Product Warranty F-7

WARRANTY
________

International Business Machines Armonk, New York,
Corporation 10504

STATEMENT OF LIMITED WARRANTY

The warranties provided by IBM in this Statement of
___________________________________________________
Limited Warranty apply only to Machines you originally
______________________________________________________
purchase for your use, and not for resale, from IBM or
______________________________________________________
your reseller. The term "Machine" means an IBM machine,
________________________________________________________
its features, conversions, upgrades, elements, or
_________________________________________________
accessories, or any combination of them. Unless IBM
____________________________________________________
specifies otherwise, the following warranties apply only
________________________________________________________
in the country where you acquire the Machine. If you
_____________________________________________________
have any questions, contact IBM or your reseller.
_________________________________________________

+-------------------------------------------------------+
| |
| MACHINE: IBM 8224 Ethernet Stackable Hub |
| |
| WARRANTY PERIOD*: One Year |
| |
| *Contact your place of purchase for warranty service |
____________________________________________________
| information. |
____________
| |
+-------------------------------------------------------+

PRODUCTION STATUS
Each Machine is manufactured from new parts, or new and
used parts. In some cases, the Machine may not be new
and may have been previously installed. Regardless of
the Machine's production status, IBM's warranty terms
apply.

THE IBM WARRANTY FOR MACHINES
IBM warrants that each Machine 1) is free from defects in
materials and workmanship and 2) conforms to IBM's
Official Published Specifications. The warranty period
for a Machine is a specified, fixed period commencing on
its Date of Installation. The date on your receipt is
the Date of Installation, unless IBM or your reseller
informs you otherwise.

During the warranty period IBM or your reseller, if
authorized by IBM, will provide warranty service under
the type of service designated for the Machine and will
manage and install engineering changes that apply to the
Machine.

For IBM or your reseller to provide warranty service for
a feature, conversion, or upgrade, IBM or your reseller
may require that the Machine on which it is installed be
1) for certain Machines, the designated, serial-numbered

F-8 8224 Ethernet Stackable Hub

Machine and 2) at an engineering-change level compatible
with the feature, conversion, or upgrade. Many of these
transactions involve the removal of parts and their
return to IBM. You represent that all removed parts are
genuine and unaltered. A part that replaces a removed
part will assume the warranty service status of the
replaced part.

If a Machine does not function as warranted during the
warranty period, IBM or your reseller will repair it or
replace it with one that is at least functionally
equivalent, without charge. The replacement may not be
new, but will be in good working order. If IBM or your
reseller is unable to repair or replace the Machine, you
may return it to your place of purchase and your money
will be refunded.

If you transfer a Machine to another user, warranty
service is available to that user for the remainder of
the warranty period. You should give your proof of
purchase and this Statement to that user. However, for
Machines which have a life-time warranty, this warranty
is not transferable.

WARRANTY SERVICE
To obtain warranty service for the Machine, you should
contact your reseller or call IBM. In the United States,
call IBM at 1-800-IBM-SERV (426-7378). In Canada, call
IBM at 1-800-565-3344. You may be required to present
proof of purchase.

IBM or your reseller will provide certain types of repair
and exchange service, either at your location or at IBM's
or your reseller's service center, to restore a Machine
to good working order.

When a type of service involves the exchange of a Machine
or part, the item IBM or your reseller replaces becomes
its property and the replacement becomes yours. You
represent that all removed items are genuine and
unaltered. The replacement may not be new, but will be
in good working order and at least functionally
equivalent to the item replaced. The replacement assumes
the warranty service status of the replaced item. Before
IBM or your reseller exchanges a Machine or part, you
agree to remove all features, parts, options,
alterations, and attachments not under warranty service.
You also agree to ensure that the Machine is free of any
legal obligations or restrictions that prevent its
exchange.

You agree to:

Appendix F. Notices and Product Warranty F-9

1. obtain authorization from the owner to have IBM or
your reseller service a Machine that you do not own;
and
2. where applicable, before service is provided --
a. follow the problem determination, problem
analysis, and service request procedures that IBM
or your reseller provide,
b. secure all programs, data, and funds contained in
a Machine, and
c. inform IBM or your reseller of changes in a
Machine's location.

IBM is responsible for loss of, or damage to, your
Machine while it is 1) in IBM's possession or 2) in
transit in those cases where IBM is responsible for the
transportation charges.

EXTENT OF WARRANTY
IBM does not warrant uninterrupted or error-free
operation of a Machine.

The warranties may be voided by misuse, accident,
modification, unsuitable physical or operating
environment, improper maintenance by you, removal or
alteration of Machine or parts identification labels, or
failure caused by a product for which IBM is not
responsible.

THESE WARRANTIES REPLACE ALL OTHER WARRANTIES OR
CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
THESE WARRANTIES GIVE YOU SPECIFIC LEGAL RIGHTS AND YOU
MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION
TO JURISDICTION. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF EXPRESS OR IMPLIED WARRANTIES,
SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO
YOU. IN THAT EVENT SUCH WARRANTIES ARE LIMITED IN
DURATION TO THE WARRANTY PERIOD. NO WARRANTIES APPLY
AFTER THAT PERIOD.

LIMITATION OF LIABILITY
Circumstances may arise where, because of a default on
IBM's part or other liability you are entitled to recover
damages from IBM. In each such instance, regardless of
the basis on which you are entitled to claim damages from
IBM (including fundamental breach, negligence,
misrepresentation, or other contract or tort claim), IBM
is liable only for:

1. damages for bodily injury (including death) and
damage to real property and tangible personal
property; and

F-10 8224 Ethernet Stackable Hub

2. the amount of any other actual direct damages or
loss, up to the greater of U.S. $100,000 or the
charges (if recurring, 12 months' charges apply) for
the Machine that is the subject of the claim.

UNDER NO CIRCUMSTANCES IS IBM LIABLE FOR ANY OF THE
FOLLOWING: 1) THIRD-PARTY CLAIMS AGAINST YOU FOR LOSSES
OR DAMAGES (OTHER THAN THOSE UNDER THE FIRST ITEM LISTED
ABOVE); 2) LOSS OF, OR DAMAGE TO, YOUR RECORDS OR DATA;
OR 3) SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY
ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR
SAVINGS), EVEN IF IBM OR YOUR RESELLER IS INFORMED OF
THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL
DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT
APPLY TO YOU.

Appendix F. Notices and Product Warranty F-11

F-12 8224 Ethernet Stackable Hub

APPENDIX G. HELP AND SERVICE INFORMATION
_________________________________________

You can get toll-free technical support 24 hours a day, 7
days a week, to answer any questions about your new 8224.

If you need warranty service, return or exchange is
available. You are entitled to on-site service for one
year from date of purchase. See "Warranty" on page F-8
for the telephone number to call for warranty service.

Before calling for technical support, please prepare for
your call by following these steps.

CAUTION: To avoid electrical shock, unplug your 8224 and all attached
devices from electrical outlets before performing any troubleshooting
procedure.

STEP 1: TROUBLESHOOTING
________________________

You might be able to solve the problem yourself. Before
calling IBM, try the following troubleshooting
procedures.

1. Test the power outlet to be sure power is present.

2. Remove and reattach all cables, checking cables,
connectors, and ports for damage.

3. Remove and reseat any MEP modules, if applicable.

STEP 2: PREPARING FOR THE CALL
_______________________________

To assist the technical support representative, have
available as much of the following information as
possible:

1. Product name, description, and serial number (if any)

2. Proof of purchase

3. Status of the LEDs

4. Exact wording of SNMP traps (if any)

5. Description of the problem

6. Hardware and software configuration information for
your system

If possible, be at your 8224. Your technical support
representative might want to walk you through the problem
during the call.

STEP 3: PLACING THE CALL TO IBM
________________________________

Call one of the following numbers:

o Within the United States, call the Options by IBM
HelpCenter at 1-800-426-7299.

o Within Canada, call HelpPC at 1-800-565-3344.

o Outside the United States and Canada, contact your
IBM HelpWare number, your place of purchase, or your
local branch office.

G-2 8224 Ethernet Stackable Hub

GLOSSARY
________

This glossary defines terms and committee drafts, and working
abbreviations used in this manual. papers being developed by
It includes terms and definitions ISO/IEC JTC1/SC1.
from the IBM Dictionary of Computing
___________________________
(New York; McGraw-Hill, Inc., 1994). This glossary uses standard
reference words for entries. They
o The symbol (A) identifies are:
definitions from the American
________
National Standard Dictionary for REFERENCE MEANING
________________________________
Information Systems, ANSI
___________________
X3.172-1990, copyright 1990 by SYNONYM FOR Appears in the
the American National Standards commentary of a
Institute (ANSI). Copies can be less desirable
purchased from the American or less specific
National Standards Institute, term and
1430 Broadway, New York, New identifies the
York 10018. preferred term
that has the
o The symbol (E) identifies same meaning.
definitions from the ANSI/EIA The less desired
________
Standard - 440A: Fiber Optic or less specific
____________________________
Terminology, copyright 1989 by term is not
___________
the Electronics Industries defined.
Association (EIA). Copies can
be purchased from the Electronic CONTRAST WITH Refers to a term
Industries Association, 2001 that has an
Pennsylvania Avenue N.W., opposite or
Washington, DC 20006. substantially
different
o The symbol (I) identifies meaning.
definitions from the Information
___________
Technology Vocabulary, developed SEE Refers to terms
_____________________
by Subcommittee 1, Joint in which this
Technical Committee 1, of the term appears.
International Organization for
Standardization and the SEE ALSO Refers to
International Electrotechnical related terms
Commission (ISO/IEC JTC1/SC1). that have
similar (but not
o The symbol (T) identifies synonymous)
definitions from draft meanings.
international standards,

+--------------------+ another node or device.
| SPECIAL CHARACTERS | (4) Currently transmitting or
+--------------------+ receiving.

&MU.M. Micrometer. One millionth ADAPTER. In a LAN, within a
part of one meter; synonymous with communicating device, a circuit card
micron. that, with its associated software
and/or microcode, enables the device
&MU.S. Microsecond. One millionth to communicate over the network.
part of one second.
ADDRESS. (1) In data communication,
the IEEE-assigned unique code or the
+----------+ unique locally administered code
| NUMERICS | assigned to each device or
+----------+ workstation connected to a network.
(2) A character, group of
10BASE-FL. An IEEE 802.3 standard characters, or a value that
for baseband Ethernet data identifies a register, a particular
transmission at 10 Mbps over optical part of storage, a data source, or a
fiber cabling. data sink. The value is represented
by one or more characters. (T)
10BASE-T. An IEEE 802.3 standard (3) To refer to a device or an item
for baseband Ethernet data of data by its address. (A) (4) The
transmission at 10 Mbps over twisted location in the storage of a
pair cabling. computer where data is stored.
(5) In word processing, the
10BASE2. An IEEE 802.3 standard for location, identified by the address
baseband Ethernet data transmission code, of a specific section of the
at 10 Mbps over thin (0.2-in. recording medium or storage. (T)
diameter) coaxial cabling. Also
called thin Ethernet. ADDRESS RESOLUTION. (1) A method
_____________
for mapping network-layer addresses
10BASE5. An IEEE 802.3 standard for to media-specific addresses.
baseband Ethernet data transmission (2) See also Address Resolution
__________________
at 10 Mbps over thick (0.4-in. Protocol (ARP).
______________
diameter) coaxial cable. Also
called thick Ethernet. ADDRESS RESOLUTION PROTOCOL (ARP).
______________
A protocol that dynamically maps
between Internet addresses, baseband
+---+ adapter addresses, X.25 addresses,
| A | and token-ring adapter addresses on
+---+ a local area network.

A. Ampere. AGENT. See Simple Network
______________
Management Protocol (SNMP) agent.
________________________________
AC. Alternating current.
ANSI. American National Standards
ACTIVE. (1) Able to communicate on Institute
the network. A network adapter is
active if it is able to transmit and ARP. Address Resolution Protocol
receive on the network.
(2) Operational. (3) Pertaining to APPLICATION. A collection of
a node or device that is connected software components used to perform
or is available for connection to

X-2 8224 Ethernet Stackable Hub

specific types of user-oriented work AUTHENTICATION FAILURE. In the
on a computer. Simple Network Management Protocol
(SNMP), a trap that may be generated
ASCII. American National Standard by an authentication entity when a
Code for Information Interchange. requesting client is not a member of
The standard code, using a coded the SNMP community.
character set consisting of 7-bit
coded characters (8 bits including AUTO-PARTITION. In Ethernet
parity check), that is used for repeaters, to shut off traffic in
information interchange among data and out of a port when the port
processing systems, data detects excessive an excessive
communication systems, and frequency or duration of collisions.
associated equipment. The ASCII set Auto-partitioned ports continue to
consists of control characters and transmit and receive, and when they
graphic characters. (A) are successful in either in a
specified amount of time, they
NOTE: IBM has defined an extension reconnect to the network
to ASCII code (characters 128-255). automatically.

ATTACH. To make a device a part of
a network logically. +---+
| B |
ATTACHING DEVICE. Any device that +---+
is physically connected to a network
and can communicate over the BANDWIDTH. (1) The difference,
network. expressed in hertz, between the
highest and the lowest frequencies
AUI. Attachment unit interface. of a range of frequencies. For
example, analog transmission by
AUTHENTICATION. (1) In computer recognizable voice telephone
security, verification of the requires a bandwidth of about
identity of a user or the user's 3000 hertz (3 kHz). (2) The
eligibility to access an object. bandwidth of an optical link
(2) In computer security, designates the information-carrying
verification that a message has not capacity of the link and is related
been altered or corrupted. (3) In to the maximum bit rate that a fiber
computer security, a process used to link can support.
verify the user of an information
system or protected resources. BAUD. (1) A unit of signaling speed
(4) A process that checks the equal to the number of discrete
integrity of an entity. conditions or signal events per
second; for example, one baud
AUTHENTICATION ENTITY. In the equals one-half dot cycle per second
Simple Network Management Protocol in Morse code, one bit per second in
(SNMP), the network management agent a train of binary signals, and one
responsible for verifying that an 3-bit value per second in a train of
entity is a member of the community signals each of which can assume one
it claims to be in. This entity is of eight different states. (A)
also responsible for encoding and (2) In asynchronous transmission,
decoding SNMP messages according to the unit of modulation rate
the authentication algorithm of a corresponding to one unit interval
given community. per second; that is, if the
duration of the unit interval is 20

Glossary X-3

milliseconds, the modulation rate is two adapters. (2) A functional unit
50 baud. (A) that connects two LANs that use the
same logical link control (LLC)
BBS. Bulletin Board System. procedures but may use the same or
different medium access control
BINARY. (1) Pertaining to a system (MAC) procedures. (T) Contrast with
of numbers to the base two; the gateway and router.
_______ ______
binary digits are 0 and 1. (A)
(2) Pertaining to a selection, BROADBAND. (1) A frequency band
choice, or condition that has two between any two non-zone
possible different values or states. frequencies. (2) A frequency band
(I) (A) divisible into several narrower
bands so that different kinds of
BIT. Either of the binary digits: 0 transmissions such as voice, video,
or 1. and data transmission can occur at
the same time. Synonymous with
BIT-TIME. (1) The time required to wideband. Contrast with baseband,
________ ________
transmit 1 bit on the network. For carrierband.
___________
example, the IBM PC Network bit-time
equals 500 nanoseconds (ns). BROADBAND LOCAL AREA NETWORK (LAN).
(2) The reciprocal of the line data A local area network (LAN) in which
rate (or network data transfer information is encoded, multiplexed,
rate). and transmitted through modulation
of a carrier. (T)
BNC. A connector used with some
coaxial cables. BROADCAST. Simultaneous
transmission of data to more than
BOOTP. Bootstrap Protocol. one destination.

BOOTSTRAP PROTOCOL (BOOTP). A BTU. British thermal unit.
protocol in the TCP/IP suite that
permits a station to transmit a BUS. (1) In a processor, a physical
request for an IP address to a facility on which data is
server and permits the server to transferred to all destinations, but
assign a station an IP address based from which only addressed
on the station's media access destinations may read in accordance
control (MAC) address. Together with appropriate conventions. (I)
with the Trivial File Transfer (2) A network configuration in which
Protocol (TFTP), BootP can also be nodes are interconnected through a
used to send files. bidirectional transmission medium.
(3) One or more conductors used for
BPS. Bits per second. transmitting signals or power. (A)

BRIDGE. (1) An attaching device BUS NETWORK. A network
that connects two LAN segments to configuration that provides a
allow the transfer of information bidirectional transmission facility
from one LAN segment to the other. to which all nodes are attached. A
A bridge may connect the LAN sending node transmits in both
segments directly by network directions to the ends of the bus.
adapters and software in a single All nodes in the path examine and
device, or may connect network may copy the message as it passes.
adapters in two separate devices
through software and use of a BYTE. (1) A string that consists of
telecommunications link between the a number of bits, treated as a unit,

X-4 8224 Ethernet Stackable Hub

and representing a character. (T) installing, operating, and managing
(2) A binary character operated upon distribution of information and
as a unit and usually shorter than a control among users of communication
computer word. (A) (3) A string that systems.
consists of a particular number of
bits, usually 8, that is treated as COMPONENT. (1) Any part of a
a unit, and that represents a network other than an attaching
character. (4) A group of 8 device, such as an IBM 8228
adjacent binary digits that Multistation Access Unit.
represent one extended binary-coded (2) Hardware or software that is
decimal interchange code (EBCDIC) part of a functional unit.
character. (5) See n-bit byte.
__________
CONFIGURATION. (1) The arrangement
of a computer system or network as
+---+ defined by the nature, number, and
| C | chief characteristics of its
+---+ functional units. More
specifically, the term may refer to
CASCADE. To connect in a series or a hardware configuration or a
in a succession of stages so that software configuration. (I) (A)
each stage derives from or acts upon (2) The devices and programs that
the product of the preceding stage. make up a system, subsystem, or
network. (3) See also system
______
COAXIAL CABLE. A cable consisting configuration.
_____________
of one conductor, usually a small
copper tube or wire, within and CONNECT. In a LAN, to physically
insulated from another conductor of join a cable from a station to an
larger diameter, usually copper access unit or network connection
tubing or copper braid. point. Contrast with attach.
______

COLLISION. (1) An unwanted CSMA/CD. Carrier sense multiple
condition that results from access with collision detection.
concurrent transmissions on a
channel. (T) (2) When a frame from a
transmitting adapter encounters any +---+
other signal in its path (frame, | D |
noise, or another type of signal), +---+
the adapter stops transmitting and a
collision is registered. DATA. (1) A representation of
facts, concepts, or instructions in
COLLISION DOMAIN. In IEEE 802.3 a formalized manner suitable for
networks, one segment or multiple communication, interpretation, or
segments that are interconnected processing by human or automatic
physically by repeaters. means. (I) (A) (2) Any
representations such as characters
COMMAND. (1) A request for or analog quantities to which
performance of an operation or meaning is or might be assigned. (A)
execution of a program. (2) A
character string from a source DATA LINK. (1) Any physical link,
external to a system that represents such as a wire or a telephone
a request for system action. circuit, that connects one or more
remote terminals to a communication
COMMUNICATION NETWORK MANAGEMENT control unit, or connects one
(CNM). The process of designing, communication control unit with

Glossary X-5

another. (2) The assembly of parts personnel to diagnose hardware
of two data terminal equipment (DTE) problems.
devices that are controlled by a
link protocol, and the DIGITAL. (1) Pertaining to data in
interconnecting data circuit, that the form of digits. (A) Contrast
enable data to be transferred from a with analog. (2) Pertaining to data
______
data source to a data sink. (I) consisting of numerical values or
NOTE: A telecommunication line is discrete units.
only the physical medium of
transmission. A data link includes DTR. Data terminal ready.
the physical medium of transmission,
the protocol, and associated devices
and programs; it is both physical +---+
and logical. | E |
+---+
DATA TERMINAL READY (DTR). A signal
specified by the EIA 232 standard EIA. Electronic Industries
that indicates that a device is Association.
switched on and ready to
communicate. EIA 232. In data communications, a
specification of the Electronic
DATA TRANSFER. (1) The result of Industries Association (EIA) that
the transmission of data signals defines the interface between data
from any data source to a data terminal equipment (DTE) and data
receiver. (2) The movement, or circuit-terminating equipment (DCE),
copying, of data from one location using serial binary data
and the storage of the data at interchange.
another location.
END DELIMITER. The last byte of a
DEFAULT. Pertaining to an token or frame, consisting of a
attribute, value, or option that is special, recognizable bit pattern.
assumed when none is explicitly
specified. EQUIPMENT RACK. A metal stand for
mounting network components, such as
DELIMITER. (1) A character used to distribution panels and IBM 8224
indicate the beginning or end of a Ethernet Stackable Hubs. Synonymous
character string. (T) (2) A bit with rack.
____
pattern that defines the beginning
or end of a frame or token on a LAN. ETHERNET. A 10-megabit baseband
local area network that allows
DESTINATION. Any point or location, multiple stations to access the
such as a node, station, or transmission medium at will without
particular terminal, to which prior coordination, avoids
information is to be sent. contention by using carrier sense
and deference, and resolves
DEVICE. (1) A mechanical, contention by using collision
electrical, or electronic detection and transmission.
contrivance with a specific purpose. Ethernet uses carrier sense multiple
(2) An input/output unit such as a access with collision detection
terminal, display, or printer. See (CSMA/CD).
also attaching device.
_________________
ETHERNET VERSION 2. Also called DIX
DIAGNOSTICS. Modules or tests used Ethernet, for DEC, Intel, and Xerox.
by computer users and service Differs from IEEE 802.3 Ethernet in

X-6 8224 Ethernet Stackable Hub

frame format only. Not an approved FOIRL. Fiber-optic inter-repeater
international standard but in more link.
widespread use than IEEE 802.3
Ethernet. FRAME. (1) The unit of transmission
in some LANs, including the IBM
Token-Ring Network and the IBM PC
+---+ Network. It includes delimiters,
| F | control characters, information, and
+---+ checking characters. (2) A housing
for machine elements. (3) In
FEATURE. A part of an IBM product synchronous data link control
that may be ordered separately by (SDLC), the vehicle for every
the customer. command, every response, and all
information that is transmitted
FIELD. On a data medium or a using SDLC procedures. Each frame
storage medium, a specified area begins and ends with a flag.
used for a particular category of
data; for example, a group of FT. (1) Foot. (2) Feet.
character positions used to enter or
display wage rates on a panel. (T) FTP. (1) File Transfer Protocol.
(2) Foiled twisted pair.
FIELD-REPLACEABLE UNIT (FRU). An
assembly that is replaced in its FRU. Field replaceable unit.
entirety when any one of its
components fails. FULLY QUALIFIED PATH NAME. In an
operating system, a file name that
FILE. A named set of records stored includes all directories and the
or processed as a unit. (T) drive in the hierarchical sequence
above the file.
FILE SERVER. A high-capacity disk
storage device or a computer that FUNCTION. (1) A specific purpose of
each computer on a network can an entity, or its characteristic
access to retrieve files that can be action. (A) (2) In data
shared among the attached computers. communications, a machine action
such as carriage return or line
FILE TRANSFER PROTOCOL (FTP). In feed.
TCP/IP, an application protocol used
for transferring files to and from FUNCTIONAL UNIT. An entity of
host computers. FTP requires a user hardware, software, or both, capable
ID and possibly a password to allow of accomplishing a specified
access to files on a remote host purpose. (I) (A)
system.

FLASH MEMORY. A data storage device +---+
that is programmable, erasable, and | G |
does not require continuous power to +---+
retain its storage. The chief
benefit of flash memory over other GATEWAY. A device and its
programmable and erasable data associated software that
storage devices is that it can be interconnect networks or systems of
reprogrammed without being removed different architectures. The
from the circuit board. connection is usually made above the
reference model network layer. For
example, a gateway allows LANs

Glossary X-7

access to System/370* host star/ring network, the location of
computers. Contrast with bridge and wiring concentrators.
______
router.
______
HZ. Hertz.
GROUP. (1) A set of related records
that have the same value for a
particular field in all records. +---+
(2) A collection of users who can | I |
share access authorities for +---+
protected resources. (3) A list of
names that are known together by a ICMP. Internet Control Message
single name. the completion of an Protocol
asynchronous operation, such as an
I/O operation. IEC. International Electrotechnical
Commission.

+---+ IEEE. Institute of Electrical and
| H | Electronics Engineers
+---+
IN. Inch.
HARDWARE. Physical equipment as
opposed to programs, procedures, INPUT/OUTPUT (I/O). (1) Pertaining
rules, and associated documentation. to a device whose parts can perform
(I) (A) an input process and an output
process at the same time. (I)
HEADER. The portion of a message (2) Pertaining to a functional unit
that contains control information or channel involved in an input
for the message such as one or more process, output process, or both,
destination fields, name of the concurrently or not, and to the data
originating station, input sequence involved in such a process.
number, character string indicating
the type of message, and priority INTERFACE. (1) A shared boundary
level for the message. between two functional units,
defined by functional
HEP. Hub expansion port. characteristics, common physical
interconnection characteristics,
HERTZ (HZ). A unit of frequency signal characteristics, and other
equal to one cycle per second. characteristics as appropriate. (I)
NOTE: In the United States, line (2) A shared boundary. An interface
frequency is 60Hz or a change in may be a hardware component to link
voltage polarity 120 times per two devices or a portion of storage
second; in Europe, line frequency is or registers accessed by two or more
50Hz or a change in voltage polarity computer programs. (A) (3) Hardware,
100 times per second. software, or both, that links
systems, programs, or devices.
HMS. Hub Management System.
INTERRUPT. (1) A suspension of a
HOP. See repeater hop. process, such as execution of a
____________
computer program caused by an
HUB. In a network, a point at which external event, and performed in
circuits are either connected or such a way that the process can be
switched. For example, in a star resumed. (A) (2) An instruction
network, the central node, or in a that directs the microprocessor to
suspend what it is doing and run a

X-8 8224 Ethernet Stackable Hub

specified routine. When the routine the establishment network via
is complete, the microprocessor bridges. (2) An entire ring or bus
resumes its original work. network without bridges.

IP. Internet Protocol. LAYER. (1) One of the seven levels
of the Open Systems Interconnection
IPX. Internetwork Packet Exchange. reference model. (2) In open
systems architecture, a collection
IPX SOCKET. Within a device of related functions that comprise
attached to an IPX network, the one level of hierarchy of functions.
address of a process, such as file Each layer specifies its own
service or diagnostics. functions and assumes that lower
level functions are provided.
ISO. International Organization for (3) In SNA, a grouping of related
Standardization functions that are logically
separate from the functions of other
layers. Implementation of the
+---+ functions in one layer can be
| J | changed without affecting functions
+---+ in other layers.

JABBERING. A condition in which a LB. Pound.
device is transmitting a frame that
is longer than the maximum allowed LED. Light-emitting diode.
length.
LINK. (1) The logical connection
JACK. A connecting device to which between nodes including the
a wire or wires of a circuit may be end-to-end link control procedures.
attached and which is arranged for (2) The combination of physical
insertion of a plug. media, protocols, and programming
that connects devices on a network.
(3) In computer programming, the
+---+ part of a program, in some cases a
| K | single instruction or an address,
+---+ that passes control and parameters
between separate portions of the
KG. Kilogram. computer program. (I) (A) (4) To
interconnect items of data or
KM. Kilometer. portions of one or more computer
programs. (5) In SNA, the
KVA. Kilovolt ampere. A unit of combination of the link connection
power. and link stations joining network
nodes.

+---+ LINK CONNECTION. (1) All physical
| L | components and protocol machines
+---+ that lie between the communicating
link stations of a link. The link
LAN. Local area network. connection may include a switched or
leased physical data circuit, a LAN,
LAN SEGMENT. (1) Any portion of a or an X.25 virtual circuit. In SNA,
LAN (for example, a single bus or the physical equipment providing
ring) that can operate independently two-way communication and error
but is connected to other parts of correction and detection between one

Glossary X-9

link station and one or more other network, in order to enable the
link stations. exchange of data between data
stations. (T)
LINK TEST. In 10BASE-T and optical
fiber based Ethernets, a signal sent MEP. Media expansion port.
back and forth between a port in a
repeater and a port in an attached MESSAGE. (1) A logical partition of
device to verify connection. the user device's data stream to and
from the adapter. (2) A group of
LOCAL AREA NETWORK (LAN). A characters and control bits
computer network located on a user's transferred as an entity.
premises within a limited
geographical area. MIB. Management Information Base.

LOCALLY ADMINISTERED ADDRESS. In a MIB BROWSER. A software tool, often
local area network, an adapter shipped with network management
address that the user can assign to applications, that allows working
override the universally with any SNMP MIB that is written in
administered address. Contrast with abstract syntax notation 1 (ASN.1).
universally administered address.
MIB OBJECT. In the Simple Network
LOGICAL CONNECTION. In a network, Management Protocol (SNMP), an
devices that can communicate or work object contained in the Management
with one another because they share Information Base (MIB).
the same protocol. See also
physical connection. MICROCODE. (1) One or more
___________________
microinstructions. (2) A code,
representing the instructions of an
+---+ instruction set, that is implemented
| M | in a part of storage that is not
+---+ program-addressable.

M. Meter. MM. Millimeter.

MAC. Medium access control. MODEM (MODULATOR/DEMODULATOR). A
device that converts digital data
MANAGEMENT INFORMATION BASE (MIB). from a computer to an analog signal
In the Simple Network Management that can be transmitted in a
Protocol (SNMP), a collection of telecommunication line, and converts
objects relating to a common the analog signal received to data
management area. See also MIB for the computer.
___
object.
______

MAU. Medium attachment unit. +---+
| N |
MEDIUM ACCESS CONTROL (MAC) +---+
PROTOCOL. In a local area network,
the part of the protocol that N-BIT BYTE. A string that consists
governs communication on the of n bits. (T)
transmission medium without concern
for the physical characteristics of NAME. An alphanumeric term that
the medium, but taking into account identifies a data set, statement,
the topological aspects of the program, or cataloged procedure.

X-10 8224 Ethernet Stackable Hub

NETVIEW. A host-based IBM licensed NONVOLATILE RANDOM ACCESS MEMORY
program that provides communication (NVRAM). Random access memory that
network management (CNM) or retains its contents after
communications and systems electrical power is shut off.
management (C&SM) services.
NULL MODEM CABLE. An EIA 232 serial
NETWORK. (1) A configuration of cable wired so two terminals can
data processing devices and software communicate without the use of
connected for information modems.
interchange. (2) An arrangement of
nodes and connecting branches. NVRAM. Nonvolatile random access
Connections are made between data memory.
stations. (T)

NETWORK LAYER. (1) In the Open +---+
Systems Interconnection reference | O |
model, the layer that provides for +---+
the entities in the transport layer
the means for routing and switching OCTET. A byte that consists of 8
blocks of data through the network bits. (T)
between the open systems in which
those entities reside. (T) (2) The OHM. A unit of measure of
layer that provides services to electrical resistance.
establish a path between systems
with a predictable quality of OPEN SYSTEMS INTERCONNECTION (OSI).
service. See Open Systems (1) The interconnection of open
____________
Interconnection (OSI). systems in accordance with specific
_____________________
ISO standards. (T) (2) The use of
NETWORK MANAGEMENT. The conceptual standardized procedures to enable
control element of a station that the interconnection of data
interfaces with all of the processing systems.
architectural layers of that station NOTE: OSI architecture establishes
and is responsible for the resetting a framework for coordinating the
and setting of control parameters, development of current and future
obtaining reports of error standards for the interconnection of
conditions, and determining if the computer systems. Network functions
station should be connected to or are divided into seven layers. Each
disconnected from the network. layer represents a group of related
data processing and communication
NETWORK MANAGER. A program or group functions that can be carried out in
of programs that is used to monitor, a standard way to support different
manage, and diagnose the problems of applications.
a network.
OPEN SYSTEMS INTERCONNECTION (OSI)
NODE. (1) Any device, attached to a ARCHITECTURE. Network architecture
network, that transmits and/or that adheres to a particular set of
receives data. (2) An end-point of ISO standards that relates to Open
a link, or a junction common to two Systems Interconnection. (T)
or more links in a network. (3) In
a network, a point where one or more OPEN SYSTEMS INTERCONNECTION (OSI)
functional units interconnect REFERENCE MODEL. A model that
transmission lines. represents the hierarchical
arrangement of the seven layers

Glossary X-11

described by the Open Systems PARTITION. Electrically disconnect
Interconnection architecture. a node from a LAN. The node remains
physically connected to the LAN.
OPERATION. (1) A defined action,
namely, the act of obtaining a PATH. (1) In a network, any route
result from one or more operands in between any two nodes. (T) (2) The
accordance with a rule that route traversed by the information
completely specifies the result for exchanged between two attaching
any permissible combination of devices in a network. (3) A command
operands. (A) (2) A program step in IBM Personal Computer Disk
undertaken or executed by a Operating System (PC DOS) and IBM
computer. (3) An action performed Operating System/2* (OS/2) that
on one or more data items, such as specifies directories to be searched
adding, multiplying, comparing, or for commands or batch files that are
moving. not found by a search of the current
directory.
OPTION. (1) A specification in a
statement, a selection from a menu, PDU. Protocol data unit
or a setting of a switch, that may
be used to influence the execution PERSONAL COMPUTER (PC). A desk-top,
of a program. (2) A hardware or free-standing, or portable
software function that may be microcomputer that usually consists
selected or enabled as part of a of a system unit, a display, a
configuration process. (3) A piece monitor, a keyboard, one or more
of hardware (such as a network diskette drives, internal fixed-disk
adapter) that can be installed in a storage, and an optional printer.
device to modify or enhance device PCs are designed primarily to give
function. independent computing power to a
single user and are inexpensively
OUTPUT DEVICE. A device in a data priced for purchase by individuals
processing system by which data can or small businesses. Examples
be received from the system. (I) (A) include the various models of the
Synonymous with output unit. IBM Personal Computers, and the IBM
___________
Personal System/2* (PS/2) computer.
OUTPUT UNIT. Synonym for output
______
device. PHYSICAL CONNECTION. The ability of
______
two connectors to mate and make
electrical contact. In a network,
+---+ devices that are physically
| P | connected can communicate only if
+---+ they share the same protocol. See
also logical connection.
__________________
PARALLEL PORT. A port that
transmits the bits of a byte in PLATFORM. (1) The operating system
parallel along the lines of the bus, environment in which a program runs.
1 byte at a time, to an I/O device. (2) In computer technology, the
On a personal computer, it is used principles on which an operating
to connect a device that uses a system is based.
parallel interface, such as a dot
matrix printer, to the computer. PLUG. (1) A connector designed to
Contrast with serial port. insert into a receptacle or socket.
___________
(2) To insert a connector into a
receptacle or socket.

X-12 8224 Ethernet Stackable Hub

PORT. (1) An access point for data REVERSE ADDRESS RESOLUTION PROTOCOL
entry or exit. (2) A connector on a (RARP). A protocol that maintains a
device to which cables for other database of mappings between
devices such as display stations and physical hardware addresses and IP
printers are attached. addresses.

POST. Power-on self-test. RFC. Request for comments.

POWER-ON SELF-TEST (POST). A series ROUTER. An attaching device that
of diagnostic tests that are run connects two LAN segments, which use
automatically each time the similar or different architectures,
computer's power is turned on. at the reference model network
layer. Contrast with bridge and
______
PROCEDURE. A set of instructions gateway.
_______
that gives a service representative
a step-by-step procedure for tracing ROUTING INFORMATION PROTOCOL (RIP).
a symptom to the cause of failure. In the Internet suite of protocols,
an interior gateway protocol used to
PROTOCOL. (1) A set of semantic and exchange intradomain routing
syntactic rules that determines the information and to determine optimum
behavior of functional units in routes between internet hosts. RIP
achieving communication. (I) (2) A determines optimum routes on the
specification for the format and basis of route metrics, not link
relative timing of information transmission speed.
exchanged between communicating
parties.
+---+
| S |
+---+ +---+
| R |
+---+ SAP. (1) Service access point.
(2) Service Advertising Protocol.
RACK. Synonym for equipment rack.
______________
SEGMENT. See cable segment, LAN
_____________ ___
RANDOM ACCESS MEMORY (RAM). A segment.
_______
computer's or adapter's volatile
storage area into which data may be SERIAL. (1) Pertaining to a process
entered and retrieved in a in which all events occur one after
nonsequential manner. the other; for example, serial
transmission of the bits of a
RECEIVE. To obtain and store character according to V24 CCITT
information transmitted from a protocol. (T) (2) Pertaining to
device. the sequential or consecutive
occurrence of two or more related
REPEATER. In a network, a device activities in a single device or
that amplifies or regenerates data channel. (A) (3) Pertaining to the
signals in order to extend the sequential processing of the
distance between attaching devices. individual parts of a whole, such as
the bits of a character or the
REPEATER HOP. Counted when a frame characters of a word, using the same
passes through a repeater or its facilities for successive
equivalent. parts. (A)

Glossary X-13

SERIAL LINE INTERNET PROTOCOL SHIELDED TWISTED PAIR (STP). An
(SLIP). A simple form of electrically conductive cable made
encapsulation for IP frames that up of one or more pairs of
enables them to travel over serial individually shielded wires with a
lines. shield over all the pairs.

SERIAL PORT. On personal computers, SIGNAL. (1) A time-dependent value
a port used to attach devices such attached to a physical phenomenon
as display devices, letter-quality for conveying data. (2) A variation
printers, modems, plotters, and of a physical quantity, used to
pointing devices such as light pens convey data.
and mice; it transmits data 1 bit at
a time. Contrast with parallel SIMPLE NETWORK MANAGEMENT PROTOCOL
________
port. (SNMP) AGENT. Software stored in
____
the device being managed that
SERVER. (1) A device, program, or exchanges Simple Network Management
code module on a network dedicated Protocol information with a network
to providing a specific service to a management station.
network. (2) On a LAN, a data
station that provides facilities to SIMPLE NETWORK MANAGEMENT PROTOCOL
other data stations. Examples are a (SNMP). In the internet suite of
file server, print server, and mail protocols, a network management
server. protocol that is used to monitor
routers and attached networks. SNMP
SERVICE ADVERTISING PROTOCOL (SAP). is an application layer protocol.
In Internetwork Packet Exchange Information on devices manages is
(IPX), a protocol that provides the defined and stored in the
following: application's Management Information
Base (MIB).
o A mechanism that allows IPX
servers on an internet to SLIP. Serial Line Internet
advertise their services by name Protocol.
and type. Servers using this
protocol have their name, SNMP. Simple Network Management
service type, and internet Protocol.
address recorded in all file
servers running NetWare. SOCKET. See IPX socket.
__________

o A mechanism that allows a SOURCE ADDRESS. A field in the
workstation to broadcast a query medium access control (MAC) frame
to discover the identities of that identifies the location from
all servers of all types, all which information is sent. Contrast
servers of a specific type, or with destination address.
___________________
the nearest server of a specific
type. SP. Standards proposal.

o A mechanism that allows a START DELIMITER. The first byte of
workstation to query any file a token or frame, consisting of a
server running NetWare to special, recognizable bit pattern.
discover the names and addresses
of all servers of a specific STATION. (1) A communication device
type. attached to a network. The term
used most often in LANs is an
attaching device or workstation.
________________ ___________

X-14 8224 Ethernet Stackable Hub

(2) An input or output point of a +---+
system that uses telecommunication | T |
facilities; for example, one or more +---+
systems, computers, terminals,
devices, and associated programs at TELECOMMUNICATION LINE. Any
a particular location that can send physical medium, such as a wire,
or receive data over a that is used to transmit data.
telecommunication line. See also
attaching device, workstation. TELEPHONE TWISTED PAIR. See
_________________ ___________
unshielded twisted pair (UTP).
_____________________________
STP. Shielded twisted pair.
TERMINAL. In data communication, a
SUBSYSTEM. A secondary or device, usually equipped with a
subordinate system, or programming keyboard and display device, capable
support, usually capable of of sending and receiving
operating independently of or information.
asynchronously with a controlling
system. TERMINAL EMULATOR. A program that
allows a device such as a
SWITCH. On an adapter, a mechanism microcomputer or personal computer
used to select a value for, enable, to enter and receive data from a
or disable a configurable option or computer system as if it were a
feature. particular type of attached
terminal.
SYNCHRONOUS. (1) Pertaining to two
or more processes that depend on the TELNET. A TCP/IP application
occurrences of a specific event such protocol that allows a workstation
as common timing signal. (I) (A) to connect to a remote host as if
(2) Occurring with a regular or locally (directly) attached.
predictable timing relationship.
TFTP. Trivial File Transfer
SYSTEM. In data processing, a Protocol.
collection of people, machines, and
methods organized to accomplish a THROUGHPUT. (1) A measure of the
set of specific functions. (I) (A) amount of work performed by a
computer system over a given period
SYSTEM CONFIGURATION. A process of time, for example, number of jobs
that specifies the devices and per day. (I) (A) (2) A measure of
programs that form a particular data the amount of information
processing system. transmitted over a network in a
given period of time. For example,
SYSTEM UNIT. (1) A part of a a network's data transfer rate is
computer that contains the usually measured in bits per second.
processing unit, and may contain
devices such as disk and diskette TIA. Telecommunications Industry
drives. (2) In an IBM personal Association.
computer, the unit that contains the
processor circuitry, ROM, RAM, and TOPOLOGY. The physical or logical
the I/O channel. It may have one or arrangement of nodes in a computer
more disk or diskette drives. network. Examples include ring
topology and bus topology.

TRANSCEIVER. Any device that can
transmit and receive traffic.

Glossary X-15

TRANSMISSION MEDIUM. (1) A physical +---+
carrier of electrical energy or | V |
electromagnetic radiation. (2) The +---+
physical medium that conveys data
between data stations; for example, V. Volt.
twisted-pair wire, optical fiber,
coaxial cable. (T) VARIABLE. (1) In computer
programming, a character or group of
TRAP. In the Simple Network characters that refers to a value
Management Protocol (SNMP), a and, in the execution of a computer
message sent by a managed node program, corresponds to an address.
(agent function) to a management (2) A quantity that can assume any
station to report an exception of a given set of values. (A)
condition.
VERSION. A separate IBM-licensed
TRIVIAL FILE TRANSFER PROTOCOL program, based on an existing
(TFTP). In TCP/IP, a protocol used IBM-licensed program, that usually
for transferring files to and from has significant new code or new
host computers. It is a simpler function.
form of the File Transfer Protocol,
requiring no authentication and VISUAL DISPLAY UNIT (VDU). A device
using less memory for storage. with a TV-like display screen,
usually equipped with a keyboard.
TWISTED PAIR. A transmission medium
that consists of two insulated
conductors twisted together to +---+
reduce noise. (T) | W |
+---+

+---+ WATT. Measurement of electrical
| U | power.
+---+
WORKSTATION. (1) An I/O device that
UNIVERSALLY ADMINISTERED ADDRESS. allows either transmission of data
The address permanently encoded in or the reception of data (or both)
an adapter at the time of from a host system, as needed to
manufacture. All universally perform a job: for example, a
administered addresses are unique. display station or printer. (2) A
Contrast with locally administered configuration of I/O equipment at
____________________
address. which an operator works. (T) (3) A
_______
terminal or microcomputer, usually
UNSHIELDED TWISTED PAIR (UTP). One one connected to a mainframe or
or more twisted pairs of copper wire network, at which a user can perform
in the unshielded voice-grade cable tasks.
commonly used to connect a telephone
to its wall jack. WRITE COMMUNITY. In SNMP, one or
more network management stations
UTP. Unshielded twisted pair. that are known to a given agent and
that are authorized to write to the
MIB.

WRITE COMMUNITY NAME. A text name
that defines the write community: a
password.

X-16 8224 Ethernet Stackable Hub

+---+ 128-byte blocks and is
| X | error-correcting.
+---+

XMODEM. A protocol for file
transfer between devices that
specifies the sending of data in

Glossary X-17

X-18 8224 Ethernet Stackable Hub

INDEX
_____

+----------+ backup ports (continued)
| NUMERICS | retention of settings in
+----------+ NVRAM 1-17
SNMP trap for 3-19
10BASE-2 balun
cabling requirements 1-16 See impedance matching device
connecting cable to port 2-5 BBS, IBM PC Company, telephone
maximum segment length 1-10 number of 3-7
10BASE-FL binary to decimal
cabling requirements 1-16 conversion C-1--C-2
connecting cable to port 2-6 BootP (Bootstrap Protocol)
maximum segment length 1-10 disabling requests 3-16
planning for 1-10--1-14 requests 3-15, 3-26
10BASE-T routers and 3-15, 3-26
cabling requirements sample IP configuration
connecting cables to ports 2-6 file 3-15
maximum segment length 1-10 sample TFTP download file 3-26
TFTP and 3-26
using to set IP address 3-11,
+---+ 3-15
| A | using to upgrade microcode 3-26
+---+ Bootstrap Protocol
See BootP
acoustic characteristics 1-20
ANDing, logically C-2
AUI +---+
cabling requirements 1-16 | C |
connecting cable to port 2-5 +---+
maximum segment length 1-10
auto-partitioning 1-2 cables
automatic discovery, IP and acceptable types 1-15--1-16
IPX 3-49 connecting
to 10BASE-FL port 2-6
to 10BASE-T ports 2-6
+---+ to 10BASE2 port 2-5
| B | to AUI port 2-5
+---+ to Com port 2-7
to FOIRL port 2-6
backup ports to HEPs 2-7
assigning 1-9 crossover
example connection 1-9 bypassing need to use 1-8
how activated 1-9 pinout diagrams for B-1--B-2
MIB object that controls 3-17 versus straight-through 1-15
procedure for assigning 3-17 equivalent distances of for
devices 1-11

cables (continued) cables (continued)
foiled twisted pair (FTP) 1-15 serial (continued)
for 10BASE-FL module 1-16 setting IP address and 3-14
for 10BASE2 media expansion port SNMP management and 3-20
module 1-16 TFTP microcode upgrades
for AUI media expansion port and 3-25
module 1-16 XMODEM microcode upgrades
for Com port 1-16 and 3-9
for FOIRL module 1-16 shielded twisted pair (STP) 1-15
for hub expansion ports 1-16 standards compliance 1-15
hub expansion straight-through versus
and hot-swapping crossover 1-15
8224s 4-1--4-2 token-ring 1-15
buses inside 1-1 unshielded twisted pair
in managed stacks 1-5 (UTP) 1-15
in unmanaged stacks 1-4 calling IBM Service G-1
maximum length of 1-1, 1-4 cascading
part number for 4-3 8224s that are segmented from a
repeater hops and 1-10 stack 1-7
splitting a stack and 3-10 example 1-4
IBM Cabling System 1-15 using the Uplink switch and 1-8
labeling 2-6 cascading, limitations of 1-4
maximum distance charts, planning
limit 1-10--1-12 See planning charts
maximum segment lengths 1-10 collision 1-2, 1-6
null-modem collision domain 1-6, 3-10
cabling for Com port 1-16 Com port
connecting to Com port 2-7 assigning IP address to 3-20
setting IP address and 3-14 cabling requirements for 1-16
SNMP management and 3-20 connecting cables to 2-7
TFTP microcode upgrades rules for setting IP address
and 3-25 for 3-13
XMODEM microcode upgrades SNMP management through 3-20
and 3-9 upgrading microcode through
optical fiber using SLIP/TFTP 3-24
equivalent distances of for using XMODEM 3-8--3-10
devices 1-11 configuration file
Ethernet planning and 1-9, meanings of lines of 3-12
1-10--1-14 rules for creating 3-12
for 10BASE-FL module 1-16 sample 3-12
for FOIRL module 1-16 contents of package 2-1
maximum distance converting IP addresses
limit 1-10--1-12 from binary to decimal C-1--C-2
power loss and 1-13 from decimal to binary C-1--C-2
power loss crossover cables
budgeting 1-13--1-14 bypassing requirement 1-15
pinout diagrams B-1--B-2 pinout diagrams for B-1--B-2
planning charts 1-20 when to use 1-15
planning charts and 1-22
serial
Com port and 1-16

X-20 8224 Ethernet Stackable Hub

+---+ FOIRL (fiber-optic inter-repeater
| D | link)
+---+ cabling requirements 1-16
connecting cable to port 2-6
decimal to binary maximum segment length 1-10
conversion C-1--C-2 planning for 1-10--1-14
default gateway forms, planning
assigning external router See planning charts
as 3-22 frame formats
assigning SLIP 8224 as 3-22 repeating 1-2
choices 3-21 SNMP management and 1-3
setting using BootP 3-16 supported E-1
setting using IPX 3-16 FRUs (field-replaceable units) 4-1
setting using XMODEM 3-12 FTP cables
dimensions of 8224 1-19 See cables, foiled twisted pair
disabling ports
MIB object that controls 3-17
procedure for 3-17 +---+
distance limit, maximum 1-10--1-12 | H |
downloading microcode +---+
See microcode, upgrading
HEPs (hub expansion ports)
benefits to using for
+---+ interconnection 1-5
| E | cabling requirements for 1-16
+---+ connecting cables to 2-7
equivalent distances for 1-11
enabling ports IBM 8224 Setup and Cabling Chart
MIB object that controls 3-17 and 1-22
procedure for 3-17 role in forming a stack 1-1
environmental requirements 1-19 HMS (Hub Management System) 1-3
equivalent distances 1-10--1-12 hot-swapping 8224s
error statistics consequences of 4-1
See statistics, error procedure for 4-1
hub expansion cables
See cables, hub expansion
+---+ hub expansion ports
| F | See HEPs
+---+ Hub Management System
See HMS
features 1-2--1-4
fiber optic cables
See cables, optical fiber +---+
fiber-optic inter-repeater link | I |
See FOIRL +---+
field-replaceable units
See FRUs IBM PC Company BBS, telephone number
foiled twisted pair (FTP) cables of 3-7
See cables, foiled twisted pair impedance matching device
(FTP) connecting at the 8224 2-6

Index X-21

impedance matching device +---+
(continued) | M |
connecting at the end +---+
station 2-6
IBM Cabling System and 1-15 Management Information Base
token-ring and 1-15 See MIB
indicators management port
See LEDs See Com port
installation procedures media expansion port module
for media expansion port cable and connector
module 2-4 requirements 1-16
for rack-mounting 2-2 choices of 1-2
for surface-mounting 2-4 installation procedure for 2-4
inter-hub control bus media expansion port, location
benefits of 1-6 of 1-1
function of 1-5--1-6 MIB (Management Information Base)
StackTable and 3-17 getting new 3-6
IP address, setting list of supported 1-3
for Com port 3-13--3-14, 3-20 listing of the IBM 8224 D-1
for other 8224s 3-15, 3-16 microcode
restrictions on 3-12 getting new 3-6
using BootP or RARP 3-15 upgrading
using IPX 3-16 MIB objects that
using XMODEM 3-11--3-15 control 3-23, 3-25
IPX sample BootP/TFTP file 3-26
disabling BootP/RARP sample XMODEM upgrade request
requests 3-16 file 3-9
using to set IP addresses 3-16 using TFTP and BootP 3-26
using TFTP and SLIP 3-24
using TFTP through any
+---+ Ethernet port 3-23
| J | using XMODEM 3-8--3-10
+---+ models 001/002/481/482, differences
between
jabber 1-2 in appearance 4-3
in manageability 1-1, 1-3--1-4
in NVRAM usage 1-17
+---+ inside hub expansion cable 1-1,
| L | 1-4, 1-5
+---+ modem
cabling requirements for Com
labeling cables 2-6 port 1-16
LEDs (light-emitting diodes) connecting to Com port 2-7
appearance during POST 2-10, 4-2 forcing DTR signals 2-7
location of 1-1, 3-4 using to get MIB 3-7
meanings of 3-4--3-6 using to get microcode 3-7
light-emitting diodes using to set IP address 3-14,
See LEDs 3-20
logically ANDing C-2 using to upgrade microcode 3-9,
3-25

X-22 8224 Ethernet Stackable Hub

mounting options 1-3, 2-2--2-4 POST (power-on self-test)
(continued)
microcode upgrading and 3-10
+---+ power requirements 1-17
| N | power-on self-test
+---+ See POST
protection, port intrusion
network management applications activating 3-48
managing 8224s 1-2 description 3-48
receiving traps 3-19 intrusion detection 3-49
supported 1-3 security 3-49
using to managing 8224s 3-10
noise emission values 1-20
nonvolatile random access memory +---+
See NVRAM | R |
null-modem cable +---+
See cables, null-modem
NVRAM (nonvolatile random access RARP (Reverse Address Resolution
memory) 1-17 Protocol)
disabling requests 3-16
requests 3-15
+---+ routers and 3-15
| O | setting IP address using 3-15
+---+ redundant connections
See backup ports
optical fiber cables repeater hops
See cables, optical fiber counting for a stack 1-10
definition of 1-4
limit of four 1-10
+---+ typical Ethernet hubs and 1-4
| P | replacement parts 4-3
+---+ Reverse Address Resolution Protocol
See RARP
package contents 2-1
parts, replacement 4-3
performance statistics +---+
See statistics, performance | S |
performance, improving 1-6, 3-10, +---+
3-17
pinout diagrams B-1--B-2 sample files
planning charts BootP configuration 3-15
instructions for filling BootP/TFTP download 3-26
out 1-20 XMODEM configuration 3-12
where they are A-1--A-2 XMODEM microcode upgrade
polarity reversal, RJ-45 request 3-9
connector 3-50 segmenting 8224s from stacks
POST (power-on self-test) collision domains and 1-8
appearance of LEDs during 2-10, consequences of 1-7
4-2 example 1-7
BootP/RARP requests and 3-15 MIB object that controls
assignment 3-17

Index X-23

segmenting 8224s from stacks SNMP (Simple Network Management
(continued) Protocol) (continued)
procedure for 3-17 traps 3-19
reasons for 1-6 space requirements 1-19
relinking splitting a stack 3-10
by cascading 1-7 stack
using other devices 1-8 definition of 1-1
SNMP requirement 1-7 inter-8224 communications
segments, maximum lengths of 1-10 and 1-5, 3-17
serial cable managed 1-1
See cables, serial maximum separation of 8224s 1-1,
Serial Line Internet Protocol 1-4
See SLIP of Model xx1s 1-4
serial port of Model xx1s and xx2s 1-5
See Com port planning using the IBM 8224 Stack
service information, Chart 1-21
warranty G-1--G-2 repeater hops and 1-10
Service, calling IBM G-1 segmenting 8224s from 3-17
servicing 8224s 4-1--4-2, G-1--G-2 space requirements for 1-19
setting an IP address splitting 3-10
See IP address, setting understanding
setting up the 8224 2-1--2-10 segmenting 1-7--1-8
shielded twisted pair (STP) cables unmanaged 1-1
See cables, shielded twisted pair StackTable MIB object 3-22
(STP) inter-8224 communications
Simple Network Management Protocol and 3-17
See SNMP using to set default gateway
SLIP (Serial Line Internet Protocol) address 3-15, 3-22
assigning a default gateway using to set other 8224's IP
for 3-21--3-23 addresses 3-16
configuring 3-20 statistics
starting a session 3-20 error
TFTP and 3-24 list of available 3-18
using to manage through the Com MIB objects that contain 3-18
port 3-20 performance
using to upgrade microcode 3-24 list of available 3-18
SNMP (Simple Network Management MIB objects that contain 3-18
Protocol) STP cables
See also MIB, traps See cables, shielded twisted pair
differences between models straight-through cables 1-15, B-1
and 1-1
Ethernet frame formats and 1-3
management applications 1-2 +---+
management through the Com | T |
port 3-20--3-23 +---+
managing 8224s using 3-16--3-25
preparing to use 3-10--3-16 TFTP (Trivial File Transfer
supported MIBs 1-3 Protocol)
TFTP microcode upgrades BootP and 3-26
and 3-23, 3-24 upgrading microcode using
through Com port 3-24

X-24 8224 Ethernet Stackable Hub

TFTP (Trivial File Transfer weight of 8224 1-19
Protocol) (continued) worksheets, planning
upgrading microcode using See planning charts
(continued)
through Ethernet ports 3-23
traps, SNMP +---+
meanings of 3-19 | X |
receiving 3-19 +---+
Trivial File Transfer Protocol
See TFTP XMODEM
troubleshooting G-1 sample IP configuration
file 3-12
setting IP address using 3-11
+---+ upgrading microcode using 3-8
| U |
+---+

unshielded twisted pair (UTP) cables
See cables, unshielded twisted
pair (UTP)
upgrading microcode
See microcode, upgrading
Uplink switch
cascading and 1-8, 1-15
in planning chart 1-22
setting 2-6, 4-2
UTP cables
See cables, unshielded twisted
pair

+---+
| V |
+---+

VT100
communication interfaces 3-27
managing 8224s using 3-27--3-47
screens 3-28
starting a session 3-27

+---+
| W |
+---+

warranty service
information G-1--G-2
warranty, statement of F-8--F-11

Index X-25

IBM

Part Number: 85H5112

Printed in U.S.A.